Skip to content
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

[HTML] default exports don't respect @internal or @ignore JSDoc tags #590

Open
nberlette opened this issue May 28, 2024 · 1 comment
Open

Comments

@nberlette
Copy link

When using deno doc for JSON or stdout output, anything I have tagged with @ignore or @internal is stripped from the generated documentation (as expected). It's not the same for generated HTML docs however, at least not when it comes to default exports from a module.

For some background here, I personally dislike the docs that are generated for modules with both named exports and a default export. It's redundant and also unclear, IMO, since the default don't really convey to the user that it's an alias for an item that's also exported by name. To an inexperienced user, they might think that "default" is actually a named import with the way the docs are presented currently.

Furthermore, the generated "usage" for default exports is obnoxious. It suggests that I use the code import . from "capitalize.ts"; (but that's a topic for another issue).

Getting back to the issue at hand, I've added /** @ignore */ and /** @internal */ (and even both) to my default exports in an attempt to exclude them from the generated docs. All with no effect.

Note: Based on a cursory scanning of the currently open issues, this seems potentially related to #522.

@crowlKats
Copy link
Member

crowlKats commented Oct 4, 2024

The default exports usage was fixed, however it wasn't perfect. this is improved in #642

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants