fix(linter/explicit-module-boundary-types): fix false positives for satisfies-wrapped members#20439
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
This run croaked 😵 The workflow encountered an error before any progress could be reported. Please check the link below for details. |
Merge activity
|
There was a problem hiding this comment.
Pull request overview
Fixes explicit-module-boundary-types false positives when exported members are function expressions wrapped in TS “typing” syntax (notably satisfies, plus as / type assertions), so the rule doesn’t require explicit parameter/return annotations in cases where the wrapper already provides the type.
Changes:
- Skip visiting wrapped arrow/function expressions inside
as,satisfies, and type-assertion expressions to avoid reporting missing argument/return types. - Add helper to detect function expressions under parens / non-null wrappers.
- Extend test coverage with
satisfies-wrapped members in object literals and class fields.
You can also share your feedback on Copilot code review. Take the survey.
…atisfies-wrapped members (#20439)
bdbe9d4 to
6a307d1
Compare


No description provided.