[Snyk] Upgrade eslint-plugin-react from 7.19.0 to 7.37.1 #1238
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.
Snyk has created this PR to upgrade eslint-plugin-react from 7.19.0 to 7.37.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 65 versions ahead of your current version.
The recommended version was released on 25 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-PATHPARSE-1077067
Release notes
Package name: eslint-plugin-react
Fixed
d.ts
files (#3836 @ ljharb)Changed
Added
no-unescaped-entities
: add suggestions (#3831 @ StyleShit)forbid-component-props
: addallowedForPatterns
/disallowedForPatterns
options (#3805 @ Efimenko)no-unstable-nested-components
: addpropNamePattern
to support custom render prop naming conventions (#3826 @ danreeves)Changed
Fixed
no-is-mounted
: fix logic in method name check (#3821 @ Mathias-S)jsx-no-literals
: Avoid crashing on valueless boolean props (#3823 @ reosarevok)Added
no-string-refs
: allow this.refs in > 18.3.0 (#3807 @ henryqdineen)jsx-no-literals
AddelementOverrides
option and the ability to ignore this rule on specific elements (#3812 @ Pearce-Ropion)forward-ref-uses-ref
: add rule for checking ref parameter is added ([#3667][] @ NotWoods)Fixed
function-component-definition
,boolean-prop-naming
,jsx-first-prop-new-line
,jsx-props-no-multi-spaces
,propTypes
: use type args (#3629 @ HenryBrown0)jsx-props-no-spreading
: addexplicitSpread
option to schema (#3799 @ ljharb)Changed
no-danger
: update broken link (#3817 @ lucasrmendonca)button-has-type
: add test case with spread (#3731 @ y-hsgw)Fixed
jsx-curly-brace-presence
: avoid autofixing attributes with double quotes to a double quoted attribute (#3814 @ ljharb)Fixed
jsx-curly-brace-presence
: do not trigger on strings containing a quote character (#3798 @ akulsr0)Added
jsx-props-no-spread-multi
(#3724 @ SimonSchick)forbid-component-props
: addpropNamePattern
to allow / disallow prop name patterns (#3774 @ akulsr0)jsx-handler-names
: support ignoring component names (#3772 @ akulsr0)jsx-closing-tag-location
: addline-aligned
option (#3777 @ kimtaejin3)no-danger
: addcustomComponentNames
option (#3748 @ akulsr0)Fixed
no-invalid-html-attribute
: substitute placeholders in suggestion messages (#3759 @ mdjermanovic)sort-prop-types
: single line type ending without semicolon (#3784 @ akulsr0)require-default-props
: report when required props have default value (#3785 @ akulsr0)Refactors
variableUtil
: Avoid creating a single flat variable scope for each lookup (#3782 @ DanielRosenwasser)Fixed
prop-types
: fixclassName
missing in prop validation false negative (#3749 @ akulsr0)sort-prop-types
: Check for undefined before accessingnode.typeAnnotation.typeAnnotation
(#3779 @ tylerlaprade)Fixed
prop-types
: null-check rootNode before calling getScope (#3762 @ crnhrv)boolean-prop-naming
: avoid a crash with a spread prop (#3733 @ ljharb)jsx-boolean-value
:assumeUndefinedIsFalse
withnever
must not allow explicittrue
value (#3757 @ 6uliver)no-object-type-as-default-prop
: enable rule for components with many parameters (#3768 @ JulienR1)jsx-key
: incorrect behavior for checkKeyMustBeforeSpread with map callbacks (#3769 @ akulsr0)Fixed
boolean-prop-naming
: avoid a crash with a non-TSTypeReference type (#3718 @ developer-bandi)jsx-no-leaked-render
: invalid report if left side is boolean (#3746 @ akulsr0)jsx-closing-bracket-location
: message shows{{details}}
when there are no details (#3759 @ mdjermanovic)no-invalid-html-attribute
: ensure error messages are correct (#3759 @ mdjermanovic, @ ljharb)Changed
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: