Followed is a list of eslint-plugin-react that we should implement.
<br />).key props in iterators/collection literals @tatchi javascript: URLsDocumented here
react-hooks/rules-of-hooksreact-hooks/exhaustive-depsPlease comment if you want to work on one of these and I'll mark you to avoid duplicating work. Mentions next to rules indicate that someone else is working on it. If a PR isn't opened within a few days then it will be up for grabs.
A checkmark indicates an open PR.
A reference implementation of these features can be found here
I have omitted (w/ strikethrough) all the rules that are about code style. If there is a rule that shouldn't be omitted let me know but keep in mind we are not focussing on code style for now.
Will these go where most of the linter work has happened thus far? Or will these go in an expansion-pack? If they go in an expansion pack then I guess we would need an issue/PR to create the react expansion pack? I'll pick one up after I do the regex item I'm currently slated for.
@sebmck that's something I was meaning to ask you 鈽濓笍
I feel a few of these rules are quite dated and should be omitted. Specifically react/no-did-update-set-state, react/no-set-state and react/no-did-mount-set-state.
Also we need to support eslint-plugin-react-hooks.
I can try to implement react/jsx-key :)
Please don鈥檛 get started on any changes until we have consensus on the rules, expansion packs, and consult the React team so we鈥檙e following their recommended best practices.
Closing in favor of #341
@KevinKelbie I hope this list will be transferred somewhere else or at least maintained here as it progresses. It makes no sense to just leave it.
Most helpful comment
Please don鈥檛 get started on any changes until we have consensus on the rules, expansion packs, and consult the React team so we鈥檙e following their recommended best practices.