-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detailed recipe description #8
Comments
@kohlerm - This is actually a very good question. The reason we did not read the description from the recipe file is because of how yard works. As far as I know, yard reads the comments that are attached to a specific keyword (like 'define', 'attribute', 'action', etc.). A recipe does not have a specific keyword (other than in metadata.rb) which we use in the recipe file. Hence any comments within the recipe file will be parsed as if they were part of its source code. However, we can implement a custom yard tag (for example, Let me investigate more on the capabilities of yard for what else we can do. But your request is definitely possible. |
Thanks for the quick reply! I like your proposal, I will ask on the yard mailing list for advise. Oh and thanks for inventing yard-chef! Regards, |
I looked at the issue you posted to yard. We are pretty much doing what the yard owner suggests for recipes even now. We read all files inside the Thanks a lot for your encouragement on this project. Means a lot to us! |
You are welcome! I would be trying to help it implemented if I would know a little bit more about yard ... |
I can understand. We will be implementing this fix in our next dev cycle which should be beginning of next month. |
Great! |
@nitinmohan87 any progress on this? Would be nice to have this feature to properly document big recipes. By the way @kohlerm, as a workaround, you can always dynamically include a separate file in the metadata.rb file like so: recipe 'base-system::default', IO.read(File.join(Dir.pwd, 'recipes', 'default.md')) |
I apologize for the delay in coming up with this feature. We were held with higher priority stories that we never had the time to get to this. Kind of a lame excuse but that's what it is. I will try to get this done during my off time. But any contributions greatly appreciated. |
Hi, |
Should this work as of today? (does not seem to work for me) |
Sorry if that commit caused confusion. This feature is not yet implemented and I don't have a specific timeline for when it would available. Any contributions are appreciated! |
Ah yes. Thanks for the quick response. Very busy on a project currently. But If no-one else picks it up in the On Thu, Aug 21, 2014 at 8:52 PM, Nitin [email protected] wrote:
Franz-Robert van Vugt |
can you try this with 2.0? |
I'm relatively new to yard, and yard-chef, so please forgive me if this is a stupid question.
I understand that the brief description for the recipse comes from the metadata.rb file. I've got this working, but I wonder whether there is a way to also get a more detailed description, which would be documented within the recipe file probably at the top of the file.
Is this somehow possible?
The text was updated successfully, but these errors were encountered: