We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The JSDoc parsing function:
web-component-analyzer/src/analyze/util/js-doc-util.ts
Line 274 in f0bfaf1
assumes types are of this format:
/** @param {someType} someName someDescription */
which is fine, except for events. a common pattern when defining an event in JSDoc is:
/** @fires some-name {someType} */
for example, mwc does this. i do too.
related problem: if we have @fires my-event {MouseEvent}, it seems this function won't bother with it and will return any.
@fires my-event {MouseEvent}
any
is there any chance at some point this could be able to somehow resolve global types? or would that be lit-analyzer's job to lookup in its store?
The text was updated successfully, but these errors were encountered:
Add support for JSDoc syntax where type comes after name. #165
bd0cff3
ece154f
Add support event types in JSDoc. Fixes #165
b0815df
ad0910b
d802a91
No branches or pull requests
The JSDoc parsing function:
web-component-analyzer/src/analyze/util/js-doc-util.ts
Line 274 in f0bfaf1
assumes types are of this format:
which is fine, except for events. a common pattern when defining an event in JSDoc is:
for example, mwc does this. i do too.
related problem: if we have
@fires my-event {MouseEvent}
, it seems this function won't bother with it and will returnany
.is there any chance at some point this could be able to somehow resolve global types? or would that be lit-analyzer's job to lookup in its store?
The text was updated successfully, but these errors were encountered: