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
add @stability tag #1449
Comments
Notice that you could add those tags and they will be exported to the output AST if you include :
in the config. What you want is that the default theme to show this info right ? I guess the idea for this custom things is that you fork the theme and do it in your custom theme... |
I think we still need this basic feature. Unknown tags are not covering the requirement completely. |
I've seen some places that made up their own |
This would be great. I'm a bit surprised this doesn't exist. |
agree, our team would love an @experimental tag. it'd be nice if we could use jsdocs to communicate that something is in beta and it would encourage people to eagerly provide feedback |
I think It would be great to have a tag marking the stability level of a module or its parts.
We do have
@version
but that is really meant or numbers, and I can only imagine using it for an entire module. Version numbers (usually) follow SemVer and have an objective meaning in terms of compatibility.Contrarily, stability is more of a subjective description, but does provide meaningful information (perhaps author-defined) to users about how stable a component is.
@deprecated
is slightly helpful, but not nearly as flexible. In a module having one version number, there may be many components, each with its own stability level, and each could ascend or descend as the project grows (as opposed to version numbers, which strictly ascend).Some good examples of stability levels can be found in Node.js’s API documentation.
A new
@stability
tag would allow authors to define their own stability levels ("obsolete", "deprecated", "experimental", "locked", "frozen", etc.) and explicitly describe the meaning of each.The text was updated successfully, but these errors were encountered: