This article builds upon a previous discussion of state management using Unstated, exploring Unstated-Next, its successor. Unstated-Next leverages React Hooks and the Context API for streamlined state management, offering a more efficient approach than its predecessor, especially given the advancements in React Hooks. We'll examine single and multi-component state management using Unstated-Next. Familiarity with the previous Unstated article is helpful but not strictly required.
Minimal Form Component Example
We'll create a simple React form with a text input for a name and a submit button. Upon submission, the name will be displayed above the form. The complete code is available on GitHub. This example utilizes Create React App and Bootstrap.
First, set up the project:
npx create-react-app unstated-next-form cd unstated-next-form
Install Unstated-Next:
# yarn yarn add unstated-next # npm npm install --save unstated-next
Import necessary modules into App.js
:
// src/App.js import React, { useState } from 'react'; import { createContainer } from "unstated-next";
Create a custom hook:
// src/App.js // ...previous imports const useForm = () => { const [input, setValue] = useState(""); const [name, setName] = useState("Barney Stinson"); const handleInput = (event) => setValue(event.target.value); const updateName = (event) => { event.preventDefault(); setName(input); setValue(""); }; return { input, name, handleInput, updateName }; };
Create a container using createContainer
:
// src/App.js // ...previous code const FormContainer = createContainer(useForm);
Create the Form component:
// src/App.js // ...previous code const Form = () => { const form = FormContainer.useContainer(); return ( <div> <p>Hello! {form.name}</p> <form onsubmit="{form.updateName}"> <input type="text" value="{form.input}" onchange="{form.handleInput}"> <button type="submit">Save</button> </form> </div> ); };
Wrap the Form component with the provider in the App component:
const App = () => ( <formcontainer.provider> <form></form> </formcontainer.provider> );
This completes the minimal form example. Try building a simple to-do application using these concepts. A reference repository is available.
Sharing State Across Multiple Components
This example demonstrates sharing state between a form and a to-do list. The user's name, updated in the form, will reflect in the to-do list.
Create a new project and install dependencies:
npx create-react-app unstated-next-app cd unstated-next-app yarn add unstated-next shortid
Create store.js
to manage shared state:
// src/store.js import { useState } from "react"; import shortid from "shortid"; import { createContainer } from 'unstated-next'; const useStore = () => { const [input, setValue] = useState(""); const [name, setName] = useState("Barney Stinson"); const [todos, setTodos] = useState([{ id: 1, title: 'Write code' }, { id: 2, title: 'Buy milk' }]); const [item, setItem] = useState(""); const handleInput = (event) => setValue(event.target.value); const updateName = (event) => { event.preventDefault(); setName(input); setValue(""); }; const handleItem = (event) => setItem(event.target.value); const handleSubmit = (event) => { event.preventDefault(); setTodos([...todos, { id: shortid.generate(), title: item }]); setItem(""); }; return { input, name, handleInput, updateName, todos, item, handleItem, handleSubmit }; }; export const StoreContainer = createContainer(useStore);
Create form.js
:
// src/form.js import React from "react"; import { StoreContainer } from "./store"; const FormComponent = () => { const form = StoreContainer.useContainer(); return ( <div> <p>Hello! {form.name}</p> <form onsubmit="{form.updateName}"> <input type="text" value="{form.input}" onchange="{form.handleInput}"> <button type="submit">Change Name</button> </form> </div> ); }; export default FormComponent;
Create todo.js
:
// src/todo.js import React from "react"; import { StoreContainer } from "./store"; const TodoComponent = () => { const todo = StoreContainer.useContainer(); return ( <div> <p>Add Todos</p> <form onsubmit="{todo.handleSubmit}"> <input type="text" value="{todo.item}" onchange="{todo.handleItem}"> <button type="submit">Add</button> </form> <p>Dear {todo.name}, here are your current tasks:</p> <ul> {todo.todos.map((item) => <li key="{item.id}">{item.title}</li>)} </ul> </div> ); }; export default TodoComponent;
Update App.js
:
import React from 'react'; import TodoComponent from "./todo"; import FormComponent from "./form"; import { StoreContainer } from "./store"; function App() { return ( <storecontainer.provider> <formcomponent></formcomponent> <todocomponent></todocomponent> </storecontainer.provider> ); } export default App;
This revised example provides a more complete and functional illustration of state sharing across multiple components using Unstated-Next. Remember to handle potential errors and edge cases in a production environment.
The above is the detailed content of Managing State in React using Unstated-Next. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics









Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

TocreatestickyheadersandfooterswithCSS,useposition:stickyforheaderswithtopvalueandz-index,ensuringparentcontainersdon’trestrictit.1.Forstickyheaders:setposition:sticky,top:0,z-index,andbackgroundcolor.2.Forstickyfooters,betteruseposition:fixedwithbot

Theconic-gradient()functioninCSScreatescirculargradientsthatrotatecolorstopsaroundacentralpoint.1.Itisidealforpiecharts,progressindicators,colorwheels,anddecorativebackgrounds.2.Itworksbydefiningcolorstopsatspecificangles,optionallystartingfromadefin

The scope of CSS custom properties depends on the context of their declaration, global variables are usually defined in :root, while local variables are defined within a specific selector for componentization and isolation of styles. For example, variables defined in the .card class are only available for elements that match the class and their children. Best practices include: 1. Use: root to define global variables such as topic color; 2. Define local variables inside the component to implement encapsulation; 3. Avoid repeatedly declaring the same variable; 4. Pay attention to the coverage problems that may be caused by selector specificity. Additionally, CSS variables are case sensitive and should be defined before use to avoid errors. If the variable is undefined or the reference fails, the fallback value or default value initial will be used. Debug can be done through the browser developer

There are three ways to create a CSS loading rotator: 1. Use the basic rotator of borders to achieve simple animation through HTML and CSS; 2. Use a custom rotator of multiple points to achieve the jump effect through different delay times; 3. Add a rotator in the button and switch classes through JavaScript to display the loading status. Each approach emphasizes the importance of design details such as color, size, accessibility and performance optimization to enhance the user experience.

Mobile-firstCSSdesignrequiressettingtheviewportmetatag,usingrelativeunits,stylingfromsmallscreensup,optimizingtypographyandtouchtargets.First,addtocontrolscaling.Second,use%,em,orreminsteadofpixelsforflexiblelayouts.Third,writebasestylesformobile,the

To make the entire grid layout centered in the viewport, it can be achieved by the following methods: 1. Use margin:0auto to achieve horizontal centering, and the container needs to be set to set the fixed width, which is suitable for fixed layout; 2. Use Flexbox to set the justify-content and align-items properties in the outer container, and combine min-height:100vh to achieve vertical and horizontal centering, which is suitable for full-screen display scenarios; 3. Use CSSGrid's place-items property to quickly center on the parent container, which is simple and has good support from modern browsers, and at the same time, it is necessary to ensure that the parent container has sufficient height. Each method has applicable scenarios and restrictions, just choose the appropriate solution according to actual needs.

To create an intrinsic responsive grid layout, the core method is to use CSSGrid's repeat(auto-fit,minmax()) mode; 1. Set grid-template-columns:repeat(auto-fit,minmax(200px,1fr)) to let the browser automatically adjust the number of columns and limit the minimum and maximum widths of each column; 2. Use gap to control grid spacing; 3. The container should be set to relative units such as width:100%, and use box-sizing:border-box to avoid width calculation errors and center them with margin:auto; 4. Optionally set the row height and content alignment to improve visual consistency, such as row
