Update eslint-plugin-react 7.35.2 → 7.37.1 (minor) #250
Conversation
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
✅ Deploy Preview for firefox-devtools-react-contextmenu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.35.2 → 7.37.1) · Repo · Changelog
Release Notes
7.37.1
7.37.0
7.36.1
7.36.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 32 commits:
Update CHANGELOG and bump version[meta] do not npmignore `d.ts` files[readme] Fix shared settings linkUpdate CHANGELOG and bump version[meta] fix release workflow[readme] flat config example for react 17+[New] `no-unstable-nested-components`: add `propNamePattern` to support custom render prop naming conventions[New] `forbid-component-props`: add `allowedForPatterns`/`disallowedForPatterns` options[New] `no-unescaped-entities`: add suggestions[New] add type generation[Dev Deps] update `eslint-plugin-import`, `gfm-footnotes`[meta] fix release workflowUpdate CHANGELOG and bump version[Fix] `jsx-no-literals`: Avoid crashing on valueless boolean props[Fix] `no-is-mounted`: fix logic in method name check[actions] fix release script[meta] add missing rule linkUpdate CHANGELOG and bump version[New] add `forward-ref-uses-ref` rule for checking ref parameter[Fix] `jsx-props-no-spreading`: add `explicitSpread` option to schema[Tests] `button-has-type`: add test case with spread[types] add jsdoc type annotations[New] `jsx-no-literals` Add `elementOverrides` option and the ability to ignore this rule on specific elements[Fix] JSX pragma: fail gracefully[Docs] `no-danger`: update broken link[Fix] `jsx-max-depth`: finding JSX element in newer `@typescript-eslint/parser` versions[Fix] super type parameter resolving in newer @typescript-eslint/parser versions[Fix] `function-component-definition`, `boolean-prop-naming`, `jsx-first-prop-new-line`, `jsx-props-no-multi-spaces`, `propTypes`: use type args[Tests] add `@typescript-eslint/parser` v6, v7, v8[Tests] use `require.resolve` to get absolute paths to parsers[meta] update release workflow to prune footnotesMerge tag 'v7.35.2'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