Hooks Considered Harmful

Re:Hooks Considered Harmful by quxpar on Monday March 21, 2022 @10:53AM (#30754801)

I want people to be critical of the method du jour, but these 'production-like code examples' defy most of the modern conventions that a React dev would use. For example the fetch example seems to ignore its own prior destructuring assignment to make an awkward reference to an object property.

[ Parent | on HN ]

Re:Hooks Considered Harmful by masylum on Monday March 21, 2022 @11:00AM (#30754880)

I agree, but the problem is that when you refer an object inside a hook, the eslint exhaustive deps will tell you to add that object as a dependency. In that example, it's easily solved with destructuring `const teamId = params`, but a lot of developers will blindly follow the eslint complaint.

[ Parent | on HN ]

Re:Hooks Considered Harmful by clansimus on Monday March 21, 2022 @01:24PM (#30757027)

In that example, eslint will tell you to add `params.teamId` as a dependency, not `params`

[ Parent | on HN ]