React
1 Introduction to React
1-1 What is React?
1-2 History and Evolution of React
1-3 Key Features of React
1-4 Setting Up the Development Environment
2 JSX and Components
2-1 Introduction to JSX
2-2 Writing JSX Syntax
2-3 Creating Components
2-4 Functional vs Class Components
2-5 Props and State
3 React State Management
3-1 Understanding State
3-2 Managing State in Functional Components
3-3 Managing State in Class Components
3-4 Lifting State Up
3-5 Context API
4 React Hooks
4-1 Introduction to Hooks
4-2 useState Hook
4-3 useEffect Hook
4-4 useContext Hook
4-5 Custom Hooks
5 React Router
5-1 Introduction to React Router
5-2 Setting Up React Router
5-3 Route, Link, and NavLink
5-4 Nested Routes
5-5 Programmatic Navigation
6 Handling Events in React
6-1 Introduction to Events
6-2 Handling Events in Functional Components
6-3 Handling Events in Class Components
6-4 Synthetic Events
6-5 Event Bubbling and Capturing
7 Forms and Controlled Components
7-1 Introduction to Forms in React
7-2 Controlled Components
7-3 Handling Form Submission
7-4 Form Validation
7-5 Uncontrolled Components
8 React Lifecycle Methods
8-1 Introduction to Lifecycle Methods
8-2 Component Mounting Phase
8-3 Component Updating Phase
8-4 Component Unmounting Phase
8-5 Error Handling
9 React and APIs
9-1 Introduction to APIs
9-2 Fetching Data with useEffect
9-3 Handling API Errors
9-4 Caching API Responses
9-5 Real-time Data with WebSockets
10 React Performance Optimization
10-1 Introduction to Performance Optimization
10-2 React memo and PureComponent
10-3 useCallback and useMemo Hooks
10-4 Lazy Loading Components
10-5 Code Splitting
11 React Testing
11-1 Introduction to Testing in React
11-2 Writing Unit Tests with Jest
11-3 Testing Components with React Testing Library
11-4 Mocking Dependencies
11-5 End-to-End Testing with Cypress
12 Advanced React Patterns
12-1 Higher-Order Components (HOC)
12-2 Render Props
12-3 Compound Components
12-4 Context and Provider Pattern
12-5 Custom Hooks for Reusability
13 React and TypeScript
13-1 Introduction to TypeScript
13-2 Setting Up TypeScript with React
13-3 TypeScript Basics for React
13-4 TypeScript with Hooks
13-5 TypeScript with React Router
14 React and Redux
14-1 Introduction to Redux
14-2 Setting Up Redux with React
14-3 Actions, Reducers, and Store
14-4 Connecting React Components to Redux
14-5 Middleware and Async Actions
15 React and GraphQL
15-1 Introduction to GraphQL
15-2 Setting Up GraphQL with React
15-3 Querying Data with Apollo Client
15-4 Mutations and Subscriptions
15-5 Caching and Optimistic UI
16 React Native
16-1 Introduction to React Native
16-2 Setting Up React Native Development Environment
16-3 Building a Simple App
16-4 Navigation in React Native
16-5 Styling and Animations
17 Deployment and Best Practices
17-1 Introduction to Deployment
17-2 Deploying React Apps to GitHub Pages
17-3 Deploying React Apps to Netlify
17-4 Deploying React Apps to AWS
17-5 Best Practices for React Development
Lifting State Up in React

Lifting State Up in React

Key Concepts

Lifting State Up

Lifting State Up is a technique in React where state is moved from a child component to a common parent component. This allows multiple child components to share the same state and ensures that they are in sync. By lifting state up, you centralize the state management, making it easier to manage and update.

Shared State

Shared state refers to the state that is used by multiple components. When components need to share data, it is often beneficial to lift the state up to a parent component. This ensures that all child components receive the same data and updates when the state changes.

Parent-Child Communication

Parent-Child Communication in React involves passing data and functions from a parent component to its child components. When lifting state up, the parent component manages the state and passes it down to the child components as props. Child components can then update the state by calling functions passed down from the parent.

Example

Consider a simple temperature converter application where two input fields allow users to enter temperatures in Celsius and Fahrenheit. The two input fields need to stay in sync, meaning if one changes, the other should update accordingly.

        function TemperatureInput(props) {
            return (
                <fieldset>
                    <legend>Enter temperature in {props.scale}:</legend>
                    <input value={props.temperature} onChange={props.onTemperatureChange} />
                </fieldset>
            );
        }

        function toCelsius(fahrenheit) {
            return (fahrenheit - 32) * 5 / 9;
        }

        function toFahrenheit(celsius) {
            return (celsius * 9 / 5) + 32;
        }

        function tryConvert(temperature, convert) {
            const input = parseFloat(temperature);
            if (Number.isNaN(input)) {
                return '';
            }
            const output = convert(input);
            const rounded = Math.round(output * 1000) / 1000;
            return rounded.toString();
        }

        function Calculator() {
            const [temperature, setTemperature] = React.useState('');
            const [scale, setScale] = React.useState('c');

            const handleCelsiusChange = (e) => {
                setTemperature(e.target.value);
                setScale('c');
            };

            const handleFahrenheitChange = (e) => {
                setTemperature(e.target.value);
                setScale('f');
            };

            const celsius = scale === 'f' ? tryConvert(temperature, toCelsius) : temperature;
            const fahrenheit = scale === 'c' ? tryConvert(temperature, toFahrenheit) : temperature;

            return (
                <div>
                    <TemperatureInput scale="C" temperature={celsius} onTemperatureChange={handleCelsiusChange} />
                    <TemperatureInput scale="F" temperature={fahrenheit} onTemperatureChange={handleFahrenheitChange} />
                </div>
            );
        }
    

Analogies

Think of lifting state up as moving the control panel of a machine to a central location. Instead of each part of the machine having its own control panel, all parts now share a single control panel. This ensures that all parts operate in sync and respond to the same inputs.

Another analogy is a classroom where the teacher (parent component) manages the attendance sheet (state). The teacher passes the attendance sheet to each student (child component) to mark their attendance. When a student marks their attendance, the teacher updates the sheet, ensuring all students see the same updated information.