State Pool

Transform your React app with our state management library! Declare global and local states like variables, powered by the magic of React hooks 🪄✨

Features & Advantages

• Simple, familiar, flexible and very minimal core API but powerful
• Built-in support for state persistence
• Very easy to learn because its API is very similar to react state hook's API
• Support selecting deeply nested state
• Support creating state dynamically
• Can be used outside react components
• Doesn't wrap your app in context providers
• Very organized API, You can do almost everything with a single import

Want to see how this library is making all that possible?

Check out the full documentation at yezyilomo.github.io/state-pool

You can also try live examples Here

How it Works

1. Create a state

2. Subscribe a component(s) to the state created

3. If a component wants to update the state, it sends update request

4. When a state receives update request, it performs the update and send signal to all components subscribed to it for them to update themselves(re-render)

Installation

1npm install state-pool

Or

1yarn add state-pool

Getting Started

Using state-pool to manage state is very simple, all you need to do is

1. Create and initialize a state by using createState
2. Use your state in your component through useState hooks

These two steps summarises pretty much everything you need to use state-pool.

Below are few examples showing how to use state-pool to manage states.

1// Example 1.
2import React from 'react';
3import { createState } from 'state-pool';
4
5
6const count = createState(0);  // Create "count" state and initialize it with 0
7
8
9function ClicksCounter(props){
10    // Use "count" state
11    const [count, setCount] = count.useState();
12
13    const incrementCount = (e) => {
14        setCount(count+1)
15    }
16
17    return (
18        <div>
19            Count: {count}
20            <br/>
21            <button onClick={incrementCount}>Click</button>
22        </div>
23    );
24}
25
26ReactDOM.render(ClicksCounter, document.querySelector("#root"));

The other way to do it is using useState from state-pool

1// Example 2.
2import React from 'react';
3import { createState, useState } from 'state-pool';
4
5
6const count = createState(0);  // Create "count" state and initialize it with 0
7
8
9function ClicksCounter(props){
10    // Use "count" state
11    const [count, setCount] = useState(count);
12
13    const incrementCount = (e) => {
14        setCount(count+1)
15    }
16
17    return (
18        <div>
19            Count: {count}
20            <br/>
21            <button onClick={incrementCount}>Click</button>
22        </div>
23    );
24}
25
26ReactDOM.render(ClicksCounter, document.querySelector("#root"));

What about local state?

With state-pool, state are just like variables, if declared on a global scope, it’s a global state and if declared on local scope it’s a local state, so the difference between global state and local state in state-pool lies where you declare them just like variables.

Here is an example for managing local state

1// Example 1.
2import React from 'react';
3import { useState } from 'state-pool';
4
5
6function ClicksCounter(props){
7    // Here `useState` hook will create "count" state and initialize it with 0
8    // Note: the `useState` hook used here is impored from state-pool and not react
9    const [count, setCount] = useState(0);
10
11    const incrementCount = (e) => {
12        setCount(count+1)
13    }
14
15    return (
16        <div>
17            Count: {count}
18            <br/>
19            <button onClick={incrementCount}>Click</button>
20        </div>
21    );
22}
23
24ReactDOM.render(ClicksCounter, document.querySelector("#root"));

If you don't want state-pool's useState to collide with React's useState you can import StatePool and use the hook from there,

Here is an example

1// Example 2.
2import React from 'react';
3import StatePool from 'state-pool';
4
5
6function ClicksCounter(props){
7    // Here `useState` hook will create "count" state and initialize it with 0
8    const [count, setCount] = StatePool.useState(0);
9
10    const incrementCount = (e) => {
11        setCount(count+1)
12    }
13
14    return (
15        <div>
16            Count: {count}
17            <br/>
18            <button onClick={incrementCount}>Click</button>
19        </div>
20    );
21}
22
23ReactDOM.render(ClicksCounter, document.querySelector("#root"));

Isn't StatePool.useState the same thing as React.useState?

Definitely. not!...

Both can be used to manage local state, and that's where the similarity ends. StatePool.useState offers more features, for one it offers a simple way to update nested data unlike React.useState, it's also flexible as it's used to manage both global state and local state. So you could say React.useState is a subset of StatePool.useState.

Here is an example of StatePool.useState in action, updating nested data

1// Example 2.
2import React from 'react';
3import StatePool from 'state-pool';
4
5
6const user = StatePool.createState({name: "Yezy", age: 25});
7
8function UserInfo(props){
9    const [user, setUser, updateUser] = StatePool.useState(user);
10
11    const updateName = (e) => {
12        updateUser(user => {
13            user.name = e.target.value;
14        });
15    }
16
17    return (
18        <div>
19            Name: {user.name}
20            <br/>
21            <input type="text" value={user.name} onChange={updateName}/>
22        </div>
23    );
24}
25
26ReactDOM.render(UserInfo, document.querySelector("#root"));

With React.useState you would need to recreate user object when updating user.name, but with StatePool.useState you don't need that, you just update the value right away.

That's one advantage of using StatePool.useState but there are many more, you'll learn when going through documentation📝.

Store based example

If you have many states and you would like to organize them into a store, state-pool allows you to do that too and provides a tone of features on top of it.

Here are steps for managing state with a store

1. Create a store(which is basically a container for your state)
2. Create and initialize a state by using store.setState
3. Use your state in your component through store.useState hooks

These three steps summarises pretty much everything you need to manage state with a store.

Below are few examples of store in action

1// Example 1.
2import { createStore } from 'state-pool';
3
4
5const store = createStore();  // Create store for storing our state
6store.setState("count", 0);  // Create "count" state and add it to the store
7
8function ClicksCounter(props){
9    // Use "count" state
10    const [count, setCount] = store.useState("count");
11
12    return (
13        <div>
14            Count: {count}
15            <br/>
16            <button onClick={e => setCount(++count)}>Click</button>
17        </div>
18    );
19}

1// Example 2.
2import { createStore } from 'state-pool';
3
4
5// Instead of using createStore and store.setState,
6// you can combine store creation and initialization as follows
7
8const store = createStore({"user", {name: "Yezy", age: 25}});  // create store and initialize it with user
9
10function UserInfo(props){
11    const [user, setUser, updateUser] = store.useState("user");
12
13    const updateName = (e) => {
14        updateUser(user => {
15            user.name = e.target.value;
16        });
17    }
18
19    return (
20        <div>
21            Name: {user.name}
22            <br/>
23            <input type="text" value={user.name} onChange={updateName}/>
24        </div>
25    );
26}

State-pool doesn't enforce storing your states in a store, If you don't like using the architecture of store you can still use state-pool without it. In state-pool, store is just a container for states, so you can still use your states without it, in fact state-pool doesn’t care where you store your states as long as you can access them you're good to go.

Pretty cool, right?

Documentation 📝

Full documentation for this project is available at yezyilomo.github.io/state-pool, you are advised to read it inorder to utilize this library to the fullest. You can also try live examples here.

Running Tests

If you've forked this library and you want to run tests use the following command

1npm test