-
Notifications
You must be signed in to change notification settings - Fork 649
fix(1196): extend parameter matching with index fallback when name matching fails #1241
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
base: main
Are you sure you want to change the base?
Conversation
return xyz.p; | ||
>xyz.p : any | ||
->xyz : any | ||
+>xyz : number |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems suspect?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be treated as an error paramTagNestedWithoutTopLevelObject
However, it seems that checkUnmatchedJSDocParameters
hasn’t been migrated yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't mean it eliminates type changes, I only meant to point out that certain cases involving qualified names are not yet covered.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I mean, this all seems like an improvement in any case. But, will leave to @sandersn to double check.
Fixes #1196
Fixes #1225
ℹ️ This patch extends parameter matching by adding a fallback to index-based resolution when JSDoc parameter tag names do not match function parameter names, and also improves handling of nested array literals.
✅ Verification test - jsdocParamTagTypeLiteral