Expected behavior
No warning for directly mutating. At least from the expected updating facilitators that I specifically declare to update the main state. Like in the state-action principle.
Screenshots
Environment (please complete the following information):
OS: [e.g. Mac OS 11, Windows 10] mac 13
Node version (node --version): 14
eslint-plugin-solid version (npm list eslint-plugin-solid/yarn why eslint-plugin-solid): 0.12.1
eslint version (npm list eslint/yarn why eslint):8.42.0
Additional context
[x] I would be willing to contribute a PR to fix this issue (probably, although understanding the structure might take a while)
Thank god this is being addressed. I believe createMutable is an amazing feature no one is talking about. Being able to use reactive plain JS is incredible. But people get afraid of the warnings
Describe the bug
When I try to update a property to trigger an update, ESLint gives a warning![image](https://github.com/solidjs-community/eslint-plugin-solid/assets/5789670/dcf177f7-a518-4a56-8b6b-bb6fec733f7b)
To Reproduce
Using recommended setup and following the documentation about
createMutable
suffice to reproduce https://www.solidjs.com/docs/latest/api#createmutableExpected behavior No warning for directly mutating. At least from the expected updating facilitators that I specifically declare to update the main state. Like in the state-action principle.
Screenshots
Environment (please complete the following information):
node --version
): 14eslint-plugin-solid
version (npm list eslint-plugin-solid
/yarn why eslint-plugin-solid
): 0.12.1eslint
version (npm list eslint
/yarn why eslint
):8.42.0Additional context