> However, I share Daniel's concerns about the schema being a separate > file, particularly if we're going to ship modules with this. For > someone new to the idea, there's no visible connection between a > `validate_resource()` call and a schema file. Inline comments might > help ameliorate this (e.g., "This function loads a .schema file in the > current directory"), but that's a fragile approach. > > What if we included the schema in the manifest within the > `validate_resource()` call? This would make the connection more > explicit and avoid an extra file (and extra file /type/, which worries > me at least as much).
So using the function as apposed to the patch to core ... this is easy enough to do. And I kind of agree if we stay with the function for validation for now then it would make sense for visibility. > Once we ship this we can work on a syntax to bring it into the > language and make the full schema obsolete. I imagine this wouldn't > land until Telly, so we have some time. Indeed. ken. -- "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: http://bit.ly/puppetconfsig"; -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
