Component
general
Description
Reference documentation for this distro is published on learn.microsoft.com at https://learn.microsoft.com/javascript/api/@microsoft/opentelemetry/
Generally, the code is well documented, but there are some gaps. For example:
There are many opportunities for improvement, and there are options to configure the project so that any updates will be fully documented. The TSLint completed-docs rule could be applied to ensure that complete documentation is included with future updates.
This javascript-guidance.htm contains the content from learn.microsoft.com about how JavaScript/TypeScript libraries should be documented for best results with the generated reference documentation.
Expected Behavior
Every object property, enum member, function parameter, or object method should have a clear description in the generated reference documentation.
This will happen after the descriptions are added, the npm package is updated, and the reference docs regenerated, using the npm package as the source.
Steps to Reproduce
- Go to https://learn.microsoft.com/javascript/api/@microsoft/opentelemetry/
- Browse the documented types
Discover many missing descriptions
Environment
Not applicable
Additional Context
I usually just assign issues like this to CoPilot and it will do a pretty good job of adding descriptions.
Component
general
Description
Reference documentation for this distro is published on learn.microsoft.com at https://learn.microsoft.com/javascript/api/@microsoft/opentelemetry/
Generally, the code is well documented, but there are some gaps. For example:
There are many opportunities for improvement, and there are options to configure the project so that any updates will be fully documented. The TSLint completed-docs rule could be applied to ensure that complete documentation is included with future updates.
This javascript-guidance.htm contains the content from learn.microsoft.com about how JavaScript/TypeScript libraries should be documented for best results with the generated reference documentation.
Expected Behavior
Every object property, enum member, function parameter, or object method should have a clear description in the generated reference documentation.
This will happen after the descriptions are added, the npm package is updated, and the reference docs regenerated, using the npm package as the source.
Steps to Reproduce
Discover many missing descriptions
Environment
Not applicable
Additional Context
I usually just assign issues like this to CoPilot and it will do a pretty good job of adding descriptions.