-
-
Notifications
You must be signed in to change notification settings - Fork 792
fix(useExplicitType): rewrite top-level variables checking #5935
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
Merged
ematipico
merged 15 commits into
biomejs:main
from
sterliakov:bugfix/gh-5932-use-explicit-type
May 30, 2025
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
fe6ffe4
Rewrite useExplicitType top-level variables checking
sterliakov 01bdb93
Add missing newline
sterliakov 9792f8a
Merge remote-tracking branch 'upstream/main' into bugfix/gh-5932-use-…
sterliakov a6c1a67
Simplify
sterliakov 215fbbb
clippy
sterliakov b245e81
Update snapshots
sterliakov 1857343
Add setter tests
sterliakov f867ecf
Move faster check to the top
sterliakov 18f0805
Allow untyped callbacks inside call expressions
sterliakov f1fbfb5
Add a testcase with typed setter
sterliakov 8b63a85
Merge branch 'main' into bugfix/gh-5932-use-explicit-type
sterliakov 558ead4
Remove wrong fixme
sterliakov a09197b
Update snapshot accordingly
sterliakov 1964883
Add changeset
sterliakov a0a385c
Merge branch 'main' into bugfix/gh-5932-use-explicit-type
sterliakov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@biomejs/biome": patch | ||
| --- | ||
|
|
||
| Fixed handling of top-level variables by `useExplicitType` rule ([#5932](https://github.com/biomejs/biome/issues/5932)). Biome now allows all variables with explicit annotations, as well as variables with trivial RHS. Biome no longer emits duplicated errors when an untyped function is assigned to an untyped variable. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'll point this out in a review comment as it really makes no sense to me. Why should
namedFuncandarrowFuncbe handled differently (namedFuncrejected,arrowFuncallowed) in the following case?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.
It's a good point, unfortunately, we miss some historical facts. Perhaps you could bring this up in the original issue and continue the discussion there.