Releases: Rel1cx/eslint-react
Releases · Rel1cx/eslint-react
v1.8.2
What's Changed
🐞 Fixes
- Fixed legacy presets not being exported correctly in
@eslint-react/eslint-plugin
Full Changelog: v1.8.1...v1.8.2
v1.8.1
What's Changed
🪄 Improvements
- Enhance rule
hooks-extra/no-direct-set-state-in-use-effect
andhooks-extra/no-direct-set-state-in-use-layout-effect
to supportset
function directly passed touseCallback
anduseMemo
without explicitly calling it - Improve website and documentation
Full Changelog: v1.8.0...v1.8.1
v1.8.0
What's Changed
🐞 Fixes
- Fixed
ESLintReactSettings
type not being exported correctly - Fixed the
set
function calls that are wrapped in auseMemo
oruseCallback
like hook not being detected byhooks-extra/no-direct-set-state-in-use-effect
andhooks-extra/no-direct-set-state-in-use-layout-effect
🪄 Improvements
- Upgrade
@typescript-eslint
's packages to8.0.0
- Improve website and documentation
Full Changelog: v1.7.1...v1.8.0
v1.7.1
What's Changed
🐞 Fixes
- Fixed the spread attributes support for dom related rules
- Fixed the issue where the overridden value was retrieved when there were duplicate attributes on a JSX element
🪄 Improvements
- Rule
no-leaked-conditional-rendering
now allows a falsy boolean literal to be used on the left side of the logical expression. by @AhmedBaset in #672 - Tweaked the default settings shipped with various presets
- Overall performance improvements
New Contributors
- @AhmedBaset made their first contribution in #672
Full Changelog: v1.7.0...v1.7.1
v1.7.0
What's Changed
✨ New
- Add
settings["react-x"].polymorphicPropName
setting to specify the name of the prop that is used to determine the component type
🪄 Improvements
- Dropped the current incomplete lint support for
React.createElement
to improve performance and subsequent code maintainability
Full Changelog: v1.6.0...v1.7.0
v1.6.0
What's Changed
✨ New
- Add
controlled
setting tosettings["react-x"].additionalComponents
'attributes
object to set whether it is controlled or not - Add glob support to
settings["react-x"].additionalComponents
'name
setting - Add default settings for
react-x
settings to presets - Undeprecate rule
no-implicit-key
and improve its usefulness - Undeprecate rule
no-complicated-conditional-rendering
and rename it tono-complex-conditional-rendering
(the previous rule will still be available until the next major update to avoid breaking changes)
🐞 Fixes
no-direct-set-state-in-use-(layout?)-effect
should warn only for theset
function
🪄 Improvements
- Remove
no-direct-set-state-in-use-(layout?)-effect
from recommended presets
New Contributors
- @alex-kinokon made their first contribution in #668
Full Changelog: v1.5.30...v1.6.0
v1.5.30
What's Changed
🐞 Fixes
- Revert
changeas this format is not supported by all package managers@typescript-eslint
's packages independencies
to"^7.16.1 || ^rc-v8"
Full Changelog: v1.5.29...v1.5.30
v1.5.29
What's Changed
✨ New
- Add rule
no-prop-types
- Add rule
no-default-props
- Add experimental
settings["react-x"].additionalComponents
settings (currently only theno-unsafe-target-blank
rule uses it, but more rules will use it in the future)
🪄 Improvements
- Add rule
no-prop-types
to recommended presets - Add rule
no-default-props
to recommended presets - Remove rule
no-useless-fragment
from recommended presets - Optimize performance of rule
no-create-ref
- Change
@typescript-eslint
' packages independencies
to"^7.16.1 || ^rc-v8"
Full Changelog: v1.5.28...v1.5.29
v1.5.28
What's Changed
🐞 Fixes
- Fix false positives and negatives in rule
hooks-extra/no-direct-set-state-in-use-effect
- Fix false positives and negatives in rule
hooks-extra/no-direct-set-state-in-use-layout-effect
- Fix rule
prefer-read-only-props
reports only the first component in a file
🪄 Improvements
- Improve website and documentation
New Contributors
- @vasilii-kovalev made their first contribution in #640
Full Changelog: v1.5.27...v1.5.28
v1.5.27
What's Changed
🐞 Fixes
- Fix rule
prefer-read-only-props
that was accidentally added to the recommended type-checked presets - Fix false negatives in rule
hooks-extra/no-direct-set-state-in-use-effect
when callset
function inside a non-function scope - Fix false negatives in rule
hooks-extra/no-direct-set-state-in-use-layout-effect
when callset
function inside a non-function scope
🪄 Improvements
- Rule
no-leaked-conditional-rendering
now supports BigInt literals on the left side of the logical expression - Rule
no-leaked-conditional-rendering
now allows a truthy number literal to be used on the left side of the logical expression - Optimize bundle size
Full Changelog: v1.5.26...v1.5.27