-
Notifications
You must be signed in to change notification settings - Fork 9
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
Semicolon added after period in documentation text #11
Comments
yeah that's unfortunate :/ a workaround is to prefix the |
For even greater nonsense, add a space instead of the dot and hover... Anyway, I'm not really sure how to fix this. The But this begs the question, why is this an issue after all? When do you type lone dots in comment blocks? I can only think of two cases, the first being textual content ###*
wow, what a great variable.
###
my_var = 1 will show and the other one being typos/ syntax errors in JSDoc: ###*
@type {
x: X.
}
###
x: X which doesn't change much really both of which are somewhat forgivable. And if it's really too bad, do ###*
# wow, what a great variable.
###
my_var = 1 So unless I'm missing something, I guess this is a wontfix. Thanks for the report! |
Thanks for the response, I can live with it. 👍 |
A semicolon is added after the last period in a comment's line of text. This scuffs up the tooltip docs when hovering the documented symbol in another location.
The text was updated successfully, but these errors were encountered: