On 11/04/2014 01:04 PM, Andy Parker wrote: > > > It would also provide at lot more confidence that a manifest is 4x > safe > if it passes `puppet parser validate`. Without that you'd have to > worry > about conditional expressions silently changing their result > between 3x > and 4x. > > > The error would have to be at runtime, so puppet parser validate would > not uncover these kinds of issues (except perhaps in trivial cases > where it could be done). I have an experiment for creating a type > inference system, but it is no where near complete enough to be a > static type analysis system for puppet 4, and even then it would have > to give up in far too many cases without yet more changes to the language. Your absolutely right but `puppet master --compile localhost --manifest manifests/role/db.pp` would work. Similarly, rspec-puppet tests would catch an exception from building the catalog even if there isn't coverage of the expression result. Perhaps an option could be added to the parser face to eval expressions?
-Josh -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/5459A314.4000209%40cpan.org. For more options, visit https://groups.google.com/d/optout.
