-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Fix getter return rule #2543
Fix getter return rule #2543
Conversation
I think the better choice is to not check for TypeScript, to align with typescript-eslint Created a new issue: #2544 |
Something like that?: if ctx.source_type().is_typescript() {
return (DefinitelyReturnsOrThrowsOrUnreachable::Yes, false);
} |
I'll do the whole batch from the list. And since you're comfortable with code, you may try https://eslint.org/docs/latest/rules/no-unreachable which is the last unimplemented cfg rule. There's also constructor-super, getter-return and no-fallthrough that are all in nursery, which need some real world testing so we can bring them to the correctness category. |
Let's improve on this instead of skipping TypeScript files. |
CodSpeed Performance ReportMerging #2543 will not alter performanceComparing Summary
|
I thought about what would happen to functions that return |
I'll try to do it. But what about this PR? |
I'll get this merged once all tests pass. |
…c-project#2543) Co-authored-by: Boshen <boshenc@gmail.com>
…ript (oxc-project#2543)" This reverts commit 5d3e42e.
…ript (oxc-project#2543)" This reverts commit 5d3e42e.
…c-project#2543) Co-authored-by: Boshen <boshenc@gmail.com>
No description provided.