Closed GiyoMoon closed 6 months ago
Thanks for catching this! You're right, the problem isn't caught directly under a Fragment, just regular JSX elements. They're parsed differently by ESLint, and I didn't catch that case.
Will be a small fix—I'll have it out on the next release!
Thank you very much!
Describe the bug The plugin doesn't warn about using
.map
on a signal if the expression is directly under a fragment in the jsx.To Reproduce
Open the
./src/App.tsx
file in your IDE which is running eslint. You should notice that only one of the two.map
expressions are being noticed by eslint.Expected behavior Both
.map
expression should give eslint warnings.Screenshots![image](https://github.com/solidjs-community/eslint-plugin-solid/assets/36984337/c1e317ee-9146-4976-b72b-f0f054014b6c)
Environment (please complete the following information):
node --version
): v18.17.0eslint-plugin-solid
version (npm list eslint-plugin-solid
/yarn why eslint-plugin-solid
): 0.13.0eslint
version (npm list eslint
/yarn why eslint
): 8.47.0