On Tuesday, February 23, 2016 at 11:31:18 PM UTC+1, Ben Ford wrote: > > Would it be possible in this scheme to mark strict mode per class? I could > mark my own code as being strict and therefore get compile time failures > when I make a typo myself, but wouldn't have to enforce that on all third > party code. >
Instead of per class I'd like to be able to set it per (module)path. We use r10k and split the role and profile modules to their own modulepath (typically called 'site'), all 3rd party modules live in the standard modulepath. I could also imagine people wanting to set this per environment. Lastly, I think --strict=ignore should be --strict=off, but that's personal preference. great idea, hope to see it come to life sooner rather then later :) cheers, Walter -- 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/6c8709a0-30ae-43d8-b558-3819b4b5dd85%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
