React Custom Hooks: useLocalStorage - Simply Explained!
Вставка
- Опубліковано 28 вер 2023
- Join The Discord! → discord.cosdensolutions.io
Source Code → github.com/cosdensolutions/co...
In this video we will learn about custom React hooks, starting with useLocalStorage. This is a very useful hook that allows you to easily interact with the local storage in React. We'll create a React custom hook that will allow us to set items in the local storage, retrieve them, and remove them from the local storage. This React hook will be highly re-usable and can be used in any component!
We have Unspoken rule in some organizations: a custom hook should use another hook.
Anything else might violate the React Rules of Hooks. These rules ensure that hooks are called in the same order on every render and that they are not conditionally called. Violating these rules can lead to unexpected behavior in your components.
With respect, thank you for your videos 🫡
Plus if you want to reuse it with different key, you would have to multiply your functions, rename them, etc. What’s in the video is an example of something that shouldn’t be a custom hook, just exported function. They are also reusable.
Nice explanation. Thank you!
great job as always , by the way i have done the first try to contribute in a open source by improving the useLocalStorage Hook to Handle Multiple Keys
Brother your teaching technique daymmm🤯
Your tutorial are really helpful thanks a lot 🙏🙏🙏🙏🙏🙏🙏
Rather than return an object containing { getItem, setItem, removeItem }. If you had returned them as an array [ get, set, clear ] you could then name them in the aame way as you would using useState. You could also use the hook several times in the same component like so.
const [getName, setName, clearName] = useLocalStorage('name')
const [getAge, setAge, clearAge] = useLocalStorage('age')
You could still rename them with aliasing, but its not so nice
const { getItem: getName, setItem: setName, removeItem: clearName } = useLocalStorage('name')
const { getItem: getAge, setItem: setAge, removeItem: clearAge } = useLocalStorage('age')
I still favor the object returning because I like aliasing things that way. With arrays you can very easily mix up the order. But ideally, you'd actually make the key part of the functions, so you would only need one hook!
Very useful!! Thanks
Mann , You're Amazing
You save my day bro 🤩
Thanks for your videos.
I love this video , thank you.
Do u have a course , I would like to check it if it is in my budget :)
I think a simple and good addition would be to convert get function to generic. Because now we might as well use jsx. 😁
It doesn’t need to be a hook just a regular function will do
better a hook, to re-use it easily and also allow it to have state or other hooks inside
And what if you want to mutate more than one key ? You should call the hook again? Isnt it better if the functions receive key and value ?
Nice Explanation! The only problem: Did not explained what custom hooks are, their purpose, use cases etc. Not an ideal choice for a beginner.
You are the best
i think you need to use hooks inside the custom hook for it to be a custom hook? i think this is just a function, a helper function maybe? good video just the same :)
not necessarily. This is designed to be a custom hook, even without state. Doing it this way makes it super easy to add state later on or callbacks. If you did it in a helper function, you'd have to convert it to a hook later on anws if you wanted those things
@@cosdensolutions great great! Thanks for the reply!
it is not a requirement to use a React Hook inside a custom hook. Custom hooks can be used to encapsulate any type of logic, including stateful logic, imperative logic, and even other custom hooks. However, it is common to use React Hooks inside of custom hooks in order to reuse stateful logic across multiple components.
Haha, I like how you always kinda make way for subscribe message right there in code.
😉
is there a reason that you used the key as a parameter of the hook and not to the functions inside instead?
so you didn't have to always pass the key to every function
shouldn't this be done inside useEffect in useLocalStorage?
why indexedDB and the libraries wrapped around it, is subtlety used among the react community? i am really curios can somebody gimme an answer
Where do css class names like 'mb-2 text-3xl font-bold' come from? I'm quite new to react and they don't seem to be a bootstrap?
It's a css framework called Tailwind.
Tailwind!
Interesting!
Now tell me what is the use of this hook when we can straightaway use the built-in localStorage APIs?
It just makes it easier to handle the try catch blocks and exposes an easier api for it that is re-usable. You could also easily add additional logic to have state or effects in that hook
I don't find anything useful in the code presented until like you said, any additional logic or state implementation for realtime rendering of the localstorage data.
const { getItem: getUserItem, setItem: setUserItem, removeItem: removeUserItem } = useLocalStorage('user');
const { getItem: getTokenItem, setTokenItem, removeItem: removeTokenItem } = useLocalStorage('token');
const somethingElse = useLocalStorage('something-else');
somethingElse.getItem(); // ...
somethingElse.setItem(); // ...
somethingElse.removeItem(); // ...
// VS
localStorage.setItem('foo', 'value1');
const foo = localStorage.getItem('foo');
localStorage.removeItem('foo');
try {
localStorage.setItem('user', JSON.stringify(loggedInUser))
} catch (error) {
}
Here built-in localStorage API looks much more easier to use and the useLocalStorage hook you suggested looks just a lot more complicated to use.
Unless you add any advantages than the existing localStorage APIs, like, again, the use of states that maps to localStorage, which can then be used to show localStorage data live updating in the components, this hooks looks pretty unnecessary.
@@cosdensolutions
The order of setItems, getItems and removeItems is different in the useLocalStorage declaration than its usage. It doesn’t matter?
nope, because they are named and it's an object!
Thank you!
Just for curious it's any clean way to detect changes in the local storage?
yeah, you can add an event listener to the 'storage' event to receive updates when things change!
@@cosdensolutions Also, you can use a useEffect hook
"Intersing! However, consider this scenario: what if I wish to have multiple useLocalStorage() instances within a single file? For instance, suppose I intend to manipulate data such as key: weather with values [rain, cloud, sun] and key: wind with values [n, e, s, w]. Wouldn't it be more elegant to employ a useLocalStorage() approach, where each returned function manages its own key:value pair, offering functions like setItem(key, val), deleteItem(key), and getItem(key)?"
yes, you could change the hook to accomodate that without a problem! This was specifically just for one key to keep it simple, but definitely !
that is not a hook but a simple util function, using use* prefix won't make it into a hook if it does not store any states.
Thats a good hook, but I don't know about setting the key when calling the hook.
If you have multiple local storage items in one component you have to use the hook multiple times and then overwrite the function names.
I think I would rather not set the key directly
yeah that can also work, you could also use the hook multiple times for different keys too, but yeah it's probably better to then make the changes to a hook that accommodates multiple keys
Hi, Sometimes when i delete data from local storage i still get it in the page unless i refreshed the browser, is there any reason for this behavior?
React doesn't by default check for changes in localStorage. As far as it's concerned, nothing changed so it doesn't need to re-render. That's why it works only on reload, because that's when React will render again
@@cosdensolutions Thanks, keep up the good work
Tell us about this copilot in vsco
have video on it! called my vscode setup
You made a hook without using any react hooks inside, kinda pointless to name it useLocalStorage, its just a normal function.
This video is kept simple, but if you were to add state or effects inside, this is much better as a hook
@@cosdensolutionsmaking it a hook just limits where it can be used. Make it a function then if theres a need for it to be a hook create one
Here are some examples of when you might want to use a custom hook without using any React Hooks inside of it:
- To encapsulate imperative logic, such as making API calls or interacting with DOM elements.
- To reuse a pattern or algorithm that doesn't involve state management.
- To create a custom hook that is simply a wrapper for another function.
Why creating a custom hook when there is no hooks inside. I think you can simply create a util file and implement these as separate functions.
Because you would want to extend this further with some state and effects. This is just the simple version. This should always be a hook, helper functions are something else
Thanks for the answer@@cosdensolutions
its good, but it is only a normal function and not a hook 😢
this is the base version of it, you can add state and effects inside easily, that's the goal! This is a hook