-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Multiline comments not working in deno doc #4755
Comments
Thanks @humancalico - I would also expect the full docs to be printed in the CLI, but I expect the intention was to just print an index of docs, and allow the user to drill into further by doing That said, I think it's a bit confusing and limiting to not just display the complete documentation up front. |
@ry I guess adding |
This was done to save on space in the overview view. If I remember correctly go doc does it this way too (it even truncates function signatures). All lines should be displayed in the details view. The first line of JSDoc is also what is displayed by VS code autocomplete, so this is nothing new in JS land. Most people won’t need examples for how to use something when they are just browsing through the package’s exports. They get examples when they look at specific functions in the details view. This might be made more clear by adding I think a |
I would like to work on this bug. May you direct me, where to start. |
Fixed in #6541 |
Running
deno doc
ongives
instead of
Tests for this do exist. here
The text was updated successfully, but these errors were encountered: