Efficient State Management With Hookstate

Hey, everyone. Good morning, good afternoon, or good evening. My name is Ebenezer Dawn, advocate at JetBrains for Webster MITE. And I want to talk about efficient state management with hook state.

Okay, what's hook state? Well, it's understandable if you've not heard about hook state before. Hook state is not that old in the game. It's a state management solution for React. And one thing I really like about it, apart from hook state being flexible and it takes simplicity to a whole new level.

So I want to use this application to demo hook states. I know, I know that to do operate is the only way I could show you create read update and delete the simplest way rather than I can show you that with a state management tool like hook state for example. So right in auto job we can complete task that's updating the task. We can also delete that we can add new tasks. So do stuff. And I've decided to use two different components for this application. We have the to dew components which represents the not complete that task, that's one component, we have another component for the completed task. And these two components share the same state, raising hook state for state management.

Now, if we go back to ID right now, I'm in a starter code base, which means I'm not using hook state yet. This we have a starter js file, and then we have tasks inside of it. What if global state management was this easy? What if this is all we needed to do to manage global state, we just have a variable and its name tasks, or whatever state we want. And we export it, then we go back to different components. And all we got to do is import it and use it. Same thing with the not completed component. This is not a fixed state, this is just using JavaScript variables to export and import. You've probably used Redux before, or react context API, or RxJS and all the rest. The state management, it works, it's really efficient, state management with these tools. But it's complex. It's really complex. And I want it to be this easy. I wanted that if I want to add a new task, I have just one method like we have on line 10, like tasks.push. And then I have my new task, instead of using extra slices, reducers, actions and all the rest or the Spread Operator having a previous state and then the next state and all that.

Can I just do tasks.push and I have my new task. This is why I love HookState. Now let me go back to the main branch where I have that should be this, where I have the implementation for HookState. This is an application built with HookState. And right in the store.js file, this is how we're using HookState to create a global state.

We have store and that's equal to the create state method from add HookState slash core. So you want to install hookstate, that's npm install slash core, or yarn add HookState slash core. And why we have slash core right now is because HookState remember I said is very extensible. So we also have hookstate slash persistence, which helps us to persist states in the local stories of browser's local storage. How cool is that? But what we need right now is HookState slash core. And the create state method from HookState slash core. This is all we got to do to create a global state. And we have tasks right inside of the object for create state methods. So why I use an object is because I'm actually want to add other things to let's say this is a global store.

And I want to add other things like something else. And this is my new state right now, this is my new state I can, whatever, whatever methods, HookState makes available to store, which is which contains all the other states is also made available to tasks and to something else. So if we come over to the Apple GS file, we were adding a new task and online 12. It's that simple. So I didn't you guys we have task dot merge and a new task. That's all right now on line seven, we are using the use states hook from HookState to get the value of tax. So we want to use tax from a global store, we have const and then we're destructuring directly we can decide to say this is constate is equal to use stage and then destroy importing from dot slash store and then we decide to do store dot tasks. Yeah, but what we decided to do is destructured a really and then right here we have taxed and we can use that.

Now in HookState to get the value of a state, we need the get method. So right here we have input value that gets and that gets the value of this local state and creates an online eight, we can create global states, we can create local state and greater the state for the input value. And I just do that directly with the use states hook. I don't need the create state for this one. I wanted to be a global state. I use the Create states method. I use the use date hook and then have my local state and input value that gets gets the value of my local state. And you can see right here on line 27, where I'm setting the value of input value to be whatever I use that type inside of the input field.

And I'm using input value to set. That's all that's all I gotta do. And we have the completed component and not completely a component. Both of them use store. And all we got to do is import store from dot dot slash store, which is the store the GS file. And on line five, we have task from store. And then for completed task, we're doing in this case is we're doing using tasks that gets to get get all the tasks and raising the filter method to get just the completed tasks.

There's probably a more straightforward way to do this. But I want to show you how to work. I'm working with two different components and using that to access one store. And for we move task while we're doing with hook states to remove the task, raising the next step body from tasks to get the task we want to remove. So that is in task index. And how are we getting the task index on line nine, we have tax dot catch dot index of this is a JavaScript method. So dot index of task. And does a task we're going to be getting from the removed task function argument when we call it right here on like 21.

So remove task and tasks. So this is a particular task when we remove we get its index we use the nested variety from tasks to set the value of that particular task to none, this is how we delete something in hook state, we use the non value from hook state slash core. So we call the set method and then it's argument is none. If you want to set this to something else, say, hey, this is going to be the new value of that particular task, we want to remove the task, and we have none. And that's it. This is me using hook state to access a store, we get in all the tasks. And so we use the get method to get the value of the task. Now we're filtering to get the completed tasks. To update a task, we have the dot set methods, and then that's going to be the new value. Now to remove a task we have the non value from hook state, slash core. And that's what we're going to do to use hook state for state management. I have a longer tutorial on hook state on my YouTube channel. So yeah, you can check it out if you want to see. If you want to see more about hook state, you want something more extensive. I also have an article on the subject on hook state.

So do me a favor and check out my YouTube channel. I have other react state management tutorials. And also check me out on LinkedIn, GitHub, and Twitter, you'll find the various articles I've written on my GitHub profile. So you go to github.com slash evidence. I have a link there to all my articles.

And this has been nice. And that's me demoing state for efficient state management in react apps. Please check out hook state. It's really nice work that the team behind it are doing it fast is efficient, I've used it and it's works. It's been working well for me.

Alright, so that it see you next time.