I would like to suggest a new feature for TSDocs.dev that enhances the sharing capabilities of NPM package documentation.
Currently, when sharing a link to a specific NPM package's documentation, the visibility settings for members are always set to default.
It would be incredibly useful to have the ability to embed custom visibility settings directly into the URL.
Often, when an NPM library extends another, it inherits methods and properties that may not be relevant to the immediate documentation needs. The ability to share links to these packages with URL parameters that hide or deemphasize inherited methods and properties would be extremely valuable.
This would allow NPM package authors to share their documentation with more focus on their package's unique features, while reducing emphasis on inherited aspects
It could be implemented via URL parameters that dictate the visibility settings, providing a seamless and efficient way to share documentation with specific configurations.
I would like to suggest a new feature for TSDocs.dev that enhances the sharing capabilities of NPM package documentation.
Currently, when sharing a link to a specific NPM package's documentation, the visibility settings for members are always set to default.
It would be incredibly useful to have the ability to embed custom visibility settings directly into the URL.
Often, when an NPM library extends another, it inherits methods and properties that may not be relevant to the immediate documentation needs. The ability to share links to these packages with URL parameters that hide or deemphasize inherited methods and properties would be extremely valuable.
This would allow NPM package authors to share their documentation with more focus on their package's unique features, while reducing emphasis on inherited aspects
It could be implemented via URL parameters that dictate the visibility settings, providing a seamless and efficient way to share documentation with specific configurations.