You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.
This has been discussed many times in passing in other issues/discussions/Slack messages; creating an issue to track the addition of a cue doc command.
Would be similar in nature to go doc
The text was updated successfully, but these errors were encountered:
JSON Schema supports annotations like title, description and comments while OpenAPI(v3.1) supports summary, and tags along with existing JSON Schema annotations.
A special attribute for documentation like @doc would be helpful to resolve the doc metadata as well as the multiline docstring(or comment) below it.
@jugaadi - can you explain what you are trying to achieve here? Because it sounds like you are trying to extract documentation about certain identifiers/packages? That being the case, I suspect working with cue/ast is what you are after. Or alternatively, cue.Value.Doc() depending on how you are working with CUE.
Sorry for the misunderstanding.. Actually I was just stating my requirement for the feature. Just like JSONSchema/OpenAPI support all these constructs for documentation, it would be really helpful if cue docs support more than just line comments. For example, OpenAPI description fields support CommonMark formatting to render rich text in the generated docs.
In order to do this, I was wondering whether an attribute(@doc) is the right way to go about it so that doc tooling can take advantage of additional metadata that can be passed along with it.
This has been discussed many times in passing in other issues/discussions/Slack messages; creating an issue to track the addition of a
cue doc
command.Would be similar in nature to
go doc
The text was updated successfully, but these errors were encountered: