Update eslint-plugin-react 7.34.3 → 7.35.0 (minor) #230
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-react (7.34.3 → 7.35.0) · Repo · Changelog
Release Notes
7.35.0
7.34.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 29 commits:
Update CHANGELOG and bump version
[Fix] `require-default-props`: report when required props have default value
[Fix] `sort-prop-types`: single line type ending without semicolon
[meta] no point in supporting eslint 9.0 - 9.6 initially
[Dev Deps] update `@babel/core`, `@babel/eslint-parser`
[New] `no-danger`: add `customComponentNames` option
[New] `jsx-closing-tag-location`: add `line-aligned` option
[New] version settings: Allow react defaultVersion to be configurable
[Refactor] `variableUtil`: Avoid creating a single flat variable scope for each lookup
[New] `jsx-handler-names`: support ignoring component names
[New] `forbid-component-props`: add `propNamePattern` to allow / disallow prop name patterns
[New] support eslint v9
[actions] Don't install with `--legacy-peer-deps` in pretest check
[Fix] `no-invalid-html-attribute`: substitute placeholders in suggestion messages
[New] support eslint v9
add `tests/helpers/getRuleDefiner.js`
[Tests] test rules with ESLint v9
[Tests] `hook-use-state`: test suggestions with `messageId` instead of `desc`
[Tests] remove duplicate tests
[New] add `jsx-props-no-spread-multi`
[New] export flat configs from plugin root and fix flat config crash
Update CHANGELOG and bump version
[Fix] `sort-prop-types`: Check for undefined before accessing `node.typeAnnotation.typeAnnotation`
[patch] make TS happy
[Refactor] `sort-comp`: use Object.entries instead of for-in
[Refactor] use `hasown` instead of the larger `object.hasown`
[Refactor] avoid making a holey array
[Dev Deps] downgrade `eslint-remote-tester-repositories`
[Fix] `prop-types`: fix `className` missing in prop validation false negative
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands