On Wed, Jun 27, 2012 at 3:08 PM, Luke Kanies <[email protected]> wrote: > On Jun 27, 2012, at 1:47 PM, Nick Fagerlund wrote: > On Wednesday, June 27, 2012 12:48:16 PM UTC-7, James Turnbull wrote: >> >>> Agreed. This isn't the first time this has bitten us and we've indeed >>> conflated the docs generation and the feature checking. >> >> The best part about having the documentation embedded in the types and >> providers is that it's expressed in a Turing-complete language, so we have >> to actually LOAD THE CODE to extract it. >> >> Like I said, I'm not sure how to deal with that. :/ For manages_passwords we >> can just generate the reference on a linux VM with all the requisite >> extensions installed, but really there could be any number of things like >> this buried in there, and I bet some of them are mutually exclusive. > > What about some kind of override on the feature checking, so that when > generating docs the features aren't checked?
Way back when the Faces documentation API was designed, part of the expectation was that we would port it to other parts of the systems (like types and providers), and then add similar mechanisms to what the `help` face uses to extract documentation. That would, indeed, be looking to have a way to load all providers regardless of constraints, and generate a reference that covered all the capabilities across all the platforms. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
