Releases: solidjs-community/eslint-plugin-solid
v0.4.3
This release fixes an issue with the solid/reactivity
rule where an unnecessary warning was being raised for async functions being passed to onMount
, on
, and some event handlers.
Full Changelog: v0.4.2...v0.4.3
v0.4.2
What's Changed
- Replace experimental package with stable version by @lukahartwig in #5
This fixes an issue where the plugin couldn't resolve a dependency.
New Contributors
- @lukahartwig made their first contribution in #5
Full Changelog: v0.4.1...v0.4.2
v0.4.0
The most exciting release so far! 🎉 v0.4.0 introduces solid/reactivity
, a comprehensive lint rule that deeply analyzes your code and warns on incorrect usages of Solid's reactivity system. Think of it like a counterpoint to React's react/rules-of-hooks
; it aims to significantly ease Solid's learning curve.
A little bit of background: Solid's core principle is fine-grained reactivity, a system of state, memos, and effects that work together to efficiently update a UI from incoming events. Solid's reactive primitives, like props, signals, memos, and stores, have to be used in certain lexical scopes called "tracked scopes" so Solid can understand how to react to any changes. While this system is more flexible than some other solutions like React's Rules of Hooks, it can be confusing.
In this rule, we ensure that Solid's reactive primitives are always accessed in tracked scopes, so changes always propagate as intended.
Feedback is encouraged! Though it's tested thoroughly, If this rule is not warning on primitives it should, or warning where it shouldn't, please file an issue here.
If you need to disable solid/reactivity
for any reason, add the following to your .eslintrc
:
"solid/reactivity": "off"
Full Changelog: v0.3.1...v0.4.0
v0.3.1
What's Changed
- Fix eslint version dependency by @ProspectPyxis in #4
New Contributors
- @ProspectPyxis made their first contribution in #4
Full Changelog: v0.3.0...v0.3.1
v0.3.0
Full Changelog: v0.2.0...v0.3.0
This is a good one! ✨ This release introduces the solid/no-destructure
rule. It catches when components destructure props in
the parameter list (as is common in React), and automatically fixes the problem, even minding mergeProps
and splitProps
.
Check the docs to learn more.
solid/no-destructure
is now part of the "plugin:solid/recommended"
configuration. If you were using a previous version with
this configuration and upgrade, you may receive new lint errors.
v0.2.0
Full Changelog: v0.1.2...v0.2.0
This release brings support for ESLint v8, both as a valid peer dependency and in the test suite.
There were no changes to the recommended
configuration or to any published rules.
v0.1.2
ESLint was throwing an error when trying to load the recommended config; that's fixed. Regression test added to make sure it stays working.
v0.1.1
Initial release! This provides a good starting set of rules, all of which are applied in the recommended
configuration. Rules around reactivity are coming soon.