Jira (PDOC-55) @!puppet.type.parameter (and property) directive should be able to add metadata

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet Strings / PDOC-55 @!puppet.type.parameter (and property) directive should be able to add metadata Change By: Henrik Lindberg Team: Puppet Developer Support Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Nicholas Fagerlund (JIRA)]

Nicholas Fagerlund commented on PDOC-55

Re: @!puppet.type.parameter (and property) directive should be able to add metadata This doesn't appear to have any info about what this is for, so in short: Ruby-based types and providers can use all kinds of impenetrable metaprogramming to tersely create objects, and it seems impossible to determine what those objects are (and what their docstrings are) with a YARD-like static analysis of the code. To document things like the core Nagios types, we need an ability to explicitly override metadata for objects in a resource type.

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet Strings / PDOC-55

@!puppet.type.parameter (and property) directive should be able to add metadata

Change By: Henrik Lindberg Sprint: PDOC - Triage

Add Comment

[Jean Bond (JIRA)]

Jean Bond commented on PDOC-55

Re: @!puppet.type.parameter (and property) directive should be able to add metadata Wow. I have no idea if we still need this or not. A lot of the core types have since been moved into modules, but given the types that we still have, maybe this is part of the issue with that output being inaccurate. Consult with Strings devs.

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Jean Bond (JIRA)]

Jean Bond updated an issue

Puppet Strings / PDOC-55

@!puppet.type.parameter (and property) directive should be able to add metadata

Change By: Jean Bond Labels: generated-docs

Add Comment