Skip to content
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

feat: update one-var for class static blocks #15317

Merged
merged 1 commit into from Nov 17, 2021
Merged

Conversation

mdjermanovic
Copy link
Member

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[x] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

Refs #15016, fixes one-var.

What changes did you make? (Give an overview)

This PR fixes false positives of the one-var rule with option "always" where the rule suggests combining declarations from a class static block with declarations from the upper scope.

/* eslint one-var: ["error", "always"] */

let a;

class C {
    static {
        let b; // false positive
    }
}

Also enables autofixing declarations at the top level of class static blocks with option "never".

Is there anything you'd like reviewers to focus on?

Documentation for this rule states that it applies to functions, but it actually applies everywhere: at the top level, in functions, and in all blocks for block-scoped variables.

Fixes false positives of the `one-var` rule with option `"always"` where the rule suggests combining declarations from a class static block with declarations from the upper scope.

Also enables autofixing declarations at the top level of class static blocks with option `"never"`.

Refs #15016
@mdjermanovic mdjermanovic added rule Relates to ESLint's core rules accepted There is consensus among the team that this change meets the criteria for inclusion new syntax This issue is related to new syntax that has reached stage 4 labels Nov 15, 2021
Copy link
Member

@nzakas nzakas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nzakas nzakas merged commit 1a1bb4b into main Nov 17, 2021
@nzakas nzakas deleted the staticblocks-onevar branch November 17, 2021 01:33
@eslint-github-bot eslint-github-bot bot locked and limited conversation to collaborators May 17, 2022
@eslint-github-bot eslint-github-bot bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label May 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion new syntax This issue is related to new syntax that has reached stage 4 rule Relates to ESLint's core rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants