Definitely excited to see this stuff moving forwards. On Thursday, July 24, 2014 5:32:13 PM UTC-7, Andy Parker wrote:
> > Henrik took all of the ideas and started trying to work out what we could > do and what we couldn't. Those are in a writeup at > https://docs.google.com/a/puppetlabs.com/document/d/1mlwyaEeZqCfbF2oI1F-95cochxfe9gubjfc_BXjkOjA/edit# > > > According to that doc, syntactically we are transitioning from this: * *Instantiation* notify { hi: message => 'hello' } * *Default* Notify { message => 'greetings' } * *Override* Notify[hi] { message => 'hello there' } To this: * *Instantiation* notify { hi: message => 'hello' } * *Default* Notify { default: message => 'greetings' } * *Override* Notify[hi] { default: message => 'hello there' } This mostly makes sense except for the use of the literal "default" in the Override syntax. The term "default" implies semantics which I don't think are correct. When using an override it's often the case that previously set values are being explicitly swapped out for different ones. It seems like it would make more sense to change the placeholder word to something that reflects that values set take precedence. E.g. * *Override* Notify[hi] { override: message => 'hello there' } Is it an intentional design decision to continue to use the word "default" in the new syntax for resource overrides? ~Reid -- 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/1d192839-f8e3-4d0f-a5f8-1c790e96fca0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
