docs: add examples for block-scoped-var with class static blocks #15302
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.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] 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
block-scoped-var
.What changes did you make? (Give an overview)
This change documents examples for
block-scoped-var
with class static blocks, and adds a few tests.`There's also a change in the code, but it's only for clarity. It doesn't change the behavior of this rule, because
var
variables defined in a static block cannot be referenced outside of it. Without this change, variables defined at the top-level of a static block would have been treated as if they were defined in an upper surrounding block, but the end result would be the same.Is there anything you'd like reviewers to focus on?