Issue #6780 has been updated by Daniel Pittman.
Just to clarify: for anything that wants a type richer than "hash" or "array",
the "json" and "yaml" format on the CLI should require the target object have a
"from_#{format}" method that works, or should raise an appropriate error.
Doing anything smarter is left for later. Even "parse this from JSON into a
hash, feed the hash to `Whatever.new` is out of scope.
----------------------------------------
Feature #6780: Implement type checking/coercion for action args
https://projects.puppetlabs.com/issues/6780
Author: Pieter van de Bruggen
Status: Accepted
Priority: Normal
Assignee: Daniel Pittman
Category: Faces
Target version: 2.7.1
Affected Puppet version: 2.7.0rc1
Keywords:
Branch:
The expectation is that actions should be able to transparently have
typechecked signatures, and that automatic coercions will happen for certain
argument types.
Consider:
option "--foo FOO", String
# => option requires a string; should it automatically to_s on an array? I
suspect not...
option "--foo FOO", Puppet::Resource::Catalog
# => option requires a catalog, and should automatically convert.
# also, it should have "--foo-type TYPE", [:yaml, :pson, :string, :hash]
added...
This makes interfacing the rich type system of Ruby with the command line's
simple String-based interface simple.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
