This is a story full of wonderful new possibilities, beautiful codey things, and components clean as the mountain air. All thanks to custom react hooks ❤️
While livecoding on the ThreadCompiler project yesterday, I noticed that with hooks our logic was getting tied up with presentation. All state was local, all logic inside components, shared state was weird, and our components looked like crap.
Here's an example.
A component that takes user input from React Context using Constate, passes it through a Remark compiler, then puts the result back in context (so other components can use it), and renders the result locally.
Local result for user preview, context for
TweetButton so we can send it into the world.
What a mess 🤮
We have a
rendered state and its setter, then a
useEffect that runs on
value changes. Passes
value through Remark with custom plugins and gets the result.
Result goes into local state via
setRendered, triggering a re-render showing a user preview. Result also goes into context with
setOutput which triggers a re-render in
<TweetButton> making it ready to tweet things out. ugh
TweetButton is even worse …
We have 3 local states for success, error, and API result. A whole API call function, and some rendering. All inside this poor little component that's supposed to be a button.
Oy vey 🙄
We can clean this up with custom hooks.
Custom hooks are functions built on top of basic React Hooks. You can build them anywhere in your project, use them in a component, and it just works. 👌
Starting with the
<Tweet> component, we can take out all that logic and wrap it in a new function.
It's customary to prefix your hooks with
use. I like to put them in a directory.
We now have a
useRemark hook with local state and an effect. When
input changes it runs through
renderTweet. The promise result goes into state. We return the current
Extracting the Remark stuff itself into a
renderTweet method makes it easier to use in
<TweetButton>. You'll see.
This new custom hook makes
<Tweet> the sweet little component it was always meant to be.
Something similar happens when we extract the
<TweetButton> mess into a hook. Check this out 👇
Almost same code as before.
You've got your 3 local states, and your
sendTweets function. Moved the actual API call to a separate
sendTweet function to clean up some more.
Upon success we update the array of tweet responses, update error and success states, etc.
The hook returns an object with everything your component needs to use it. List of
success state, and a
Your button component now looks like a button ❤️
Much clearer 👌
Nothing special. You might even say "Wait that's it?"
You take your hooky mess, wrap it in a new method, call it
useSomething, and voila: that method is a React hook and you've just created a custom hook. Congratz 👏
Enjoy your week
PS: I discovered the floppotron this morning. It is amazing
Here's how it works 👇
And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Ready to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization
Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.
Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️