-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Remove the carrot (`) from the parseParams regex? #10
Comments
In a future version, you will be able to customize this to be like js-doc. Although I personally dislike that format because it's not clear to readers or parsers what's really intended. There are always exceptions where js-doc is wrong. |
What's not clear? It's always "the thing between the end of type and start of description. Whatever it be, it's always between two spaces. I'll try later the whole v1 to see what's done. |
Only on certain tags. Which is irritating, because it's not documented well. There is no official specification that I'm aware of. I tested hundreds of tags against 5 or 6 popular libs and the results were inconsistent. |
Great! Fwiw you might find this helpful: https://github.com/jonschlinkert/parse-comments/blob/master/docs/content/comparison.md. The "type" parsing was one of the most complicated parts of this. |
It can be found at https://github.com/jonschlinkert/parse-comments/blob/master/index.js#L126. And the intention of that is because it is not standard jsdoc, so syntax highlighting is different.
source code
without carrot
with carrot
notice the
val
More better would be to wrap with ` later, instead of relay on that
The text was updated successfully, but these errors were encountered: