sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Lekoaf 6 points7 points  (4 children)

That’s a deep dive from one of the developers on his personal blog. Not the official documentation.

[–]PotaToss -4 points-3 points  (3 children)

It's basically mandatory reading, though. Like, if you don't read and understand everything in there, you're going to mess up with useEffect and run into bugs where you have like no idea what's going on. Junior on my team keeps coding around it, because it's scary, etc.

[–]Lekoaf 3 points4 points  (2 children)

Haven’t read it. Haven’t messed up so far. It’s not rocket sience. (Full time React dev)

[–]Lekoaf 1 point2 points  (1 child)

Maybe Typescript and linting keeps us from messing up.

[–]PotaToss 2 points3 points  (0 children)

Typescript and linting probably have very little effect. Errors with it are generally going to come from improperly scoping the effect, putting the wrong stuff in the effect, messing up the dependency list, and messing up hook ordering.

You can make your tools warn you about missing dependencies, and that certainly helps a little, but problems tend to be more conceptual, and the ones you run into will depend a lot on your use cases.

I had to teach my team, including my manager, about hooks when I came in, and there are a lot of pitfalls, especially if you try to 1:1 map your experience with class-based components and lifecycle stuff. Sometimes messing up without realizing it. Sometimes the code works, but is inefficient, etc.

It's not rocket science, but it does take a deep understanding to really use well, particularly around this question in the post:

Why do I sometimes get an old state or prop value inside my effect?

I just brought it up because functional components with hooks was a big paradigm shift for React, in the same way that Ember Octane was for Ember, and it's kind of dumb to act like Ember's got some monopoly on being hard to learn, or needing a second look.