Issue #12277 has been updated by Henrik Lindberg.
There is no single antonym of 'require' since 'to not require' can mean that it is 'optional', 'rejected'/'unacceptable', or 'ignored'/'don't care'. The term 'optional' works for me, but does however not include direction, so would need something like 'optionally_after' and 'optionally_before'. Optionality could be expressed as (->), (<-), and (~>), (<~), but have not though about if optional notifications are meaningful or not. ---------------------------------------- Feature #12277: Add syntactic sugar for "after" to mimic "require" meta-parameter https://projects.puppetlabs.com/issues/12277#change-73102 Author: Ben Hughes Status: Needs Decision Priority: Low Assignee: J.D. Welch Category: language Target version: Affected Puppet version: Keywords: Branch: In the Puppet DSL I have found myself writing a resource with a before => meta-parameter, only to then follow it with an after => one. After does not exist and it is require. I'd like some discussion on whether we should "go Ruby" and make our language nice to use but leading to more than one way to do things, versus "Going Python" and being technically correct and one way to do things, but no one liking it, and it getting beaten up in the play ground. -- 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.
