React: What is the One-Way Data Flow and JSX Rules

react-one way flow

React is a JavaScript library/framework for building user interfaces. It has gained immense popularity due to its simplicity and flexibility.

Understanding the core concepts like one-way data flow, JSX rules, and project setup can significantly improve your React development experience.

One-Way Data Flow in React

What is Data Flow?

Data flow is the backbone of any application, dictating how information moves and transforms as it navigates through your code. In the context of React, data flow primarily concerns how state and props are managed across components. Unlike traditional two-way data binding found in frameworks like AngularJS, React adopts a one-way data flow model. This means that data has one, and only one, way to be transferred to other parts of the application.

Advantages of One-Way Data Flow

Predictability and Debugging

One-way data flow makes the application more predictable. When data changes, it flows in a single direction, making it easier to trace how components are affected. This is a lifesaver for debugging. You can easily pinpoint where the data changes, reducing the time spent hunting down elusive bugs.

Simplified Data Management

Managing state becomes more straightforward. There’s no need to sync states between different components; the data flows down from parent components to child components via props. This makes it easier to reason about your application and leads to cleaner, more maintainable code.

Implementing One-Way Data Flow

Let’s say you’re building a real-time dashboard that displays various metrics. The metrics are fetched from an API and need to be displayed in multiple components. By using one-way data flow, you can keep the fetched data in a parent component and pass it down to child components where needed. This ensures that all components are in sync and display the most current data.

Using Props and State

Here’s a simple example to demonstrate one-way data flow using props and state in a React application. We’ll create a parent component that manages the state and a child component that receives data via props.

import React, { useState } from 'react';

// Parent Component
const Dashboard = () => {
  const [metrics, setMetrics] = useState({ temperature: 72, humidity: 30 });

  return (
      <MetricsDisplay metrics={metrics} />

// Child Component
const MetricsDisplay = ({ metrics }) => {
  return (
      <p>Temperature: {metrics.temperature}°F</p>
      <p>Humidity: {metrics.humidity}%</p>

export default Dashboard;

In this example, the Dashboard component is the parent component that holds the state. The MetricsDisplay component is the child component that receives the metrics object as a prop. Any changes to metrics in the Dashboard component will automatically be reflected in MetricsDisplay, thanks to one-way data flow.

Common Pitfalls and How to Avoid Them

Direct State Mutation

One common mistake is directly mutating the state, which can lead to unexpected behavior. Always use the setState method or its equivalent when you’re using hooks.

// Bad
this.state.counter = this.state.counter + 1;

// Good
this.setState({ counter: this.state.counter + 1 });

Using Props as Initial State

Another pitfall is using props as the initial state in a way that discards updates. If you initialize state using props, make sure to update it when the props change.

// Bad
constructor(props) {
  this.state = { counter: props.initialCounter };

// Good
static getDerivedStateFromProps(props, state) {
  if (props.initialCounter !== state.initialCounter) {
    return { counter: props.initialCounter };
  return null;

Introduction to Project Setup

Setting up a React project is like laying the foundation for a building. The tools and configurations you choose will dictate the development experience, performance, and even the future scalability of your application. In this guide, we’ll explore three popular approaches to setting up a React project: Create React App, Vite, and using React frameworks like Next.js and Gatsby.

Create React App: The Traditional Way


Create React App (CRA) has been the go-to choice for many developers when it comes to setting up a new React project. It’s maintained by Facebook and provides a zero-config setup, meaning you don’t have to worry about Webpack or Babel configurations.

To install CRA, you’ll need Node.js and npm installed on your machine. Open your terminal and run the following command:

npx create-react-app my-app

This will create a new directory called my-app with all the necessary files and dependencies.

Creating a New Project

Once the installation is complete, navigate into your project folder and start the development server:

cd my-app
npm start

Your new React app should now be running on http://localhost:3000/. It’s that simple!

Vite: The Modern Alternative

Why Choose Vite?

Vite is a build tool and development server that leverages native ES modules to enable lightning-fast development and optimized builds. It’s incredibly fast, thanks to its no-bundling development approach and optimized production builds. Vite is highly extensible and comes with out-of-the-box support for TypeScript, JSX, and even Vue.js.

Setting up with Vite

To create a new React project using Vite, run the following command:

npm init @vitejs/app my-vite-app --template react

This will set up a new React project configured with Vite. To start the development server, navigate into the project directory and run:

cd my-vite-app
npm run dev

Your Vite-powered React app will be accessible at http://localhost:3000/.

Next.js and Gatsby

When to Use Them

Next.js and Gatsby are frameworks built on top of React that offer additional features like server-side rendering, static site generation, and data fetching methods. Choose Next.js when you need server-side rendering for SEO or performance optimization. Gatsby is excellent for static sites and offers a rich plugin ecosystem.

Setting up Next.js

To create a new Next.js project, run the following command:

npx create-next-app my-next-app

This will set up a new Next.js project. To start the development server, navigate into the project directory and run:

cd my-next-app
npm run dev

Your Next.js app will now be running on http://localhost:3000/.

Rules of JSX

What is JSX?

JavaScript XML (JSX) is a syntax extension for JavaScript that allows you to write HTML-like elements and structures in a JavaScript file. It’s one of the defining features of React, enabling developers to create React elements with a syntax that’s both familiar and expressive. But don’t be fooled—JSX is not HTML, and there are key differences that you should be aware of.

Differences Between JSX and HTML

While JSX may look like HTML at first glance, there are subtle differences that can trip you up if you’re not careful. For instance, JSX is case-sensitive, and certain HTML attributes have different names in JSX.

className vs class

In HTML, you’d use the class attribute to assign CSS classes to an element. However, in JSX, the attribute is called className. This is because class is a reserved keyword in JavaScript.

<div class="my-class"></div>

// JSX
<div className="my-class"></div>

Self-closing Tags

In HTML, tags like <input>, <br>, and <img> don’t need to be closed. In JSX, however, all tags must be closed. If an element doesn’t have any children, you can use a self-closing tag.

<input type="text">

// JSX
<input type="text" />

Writing JSX Code

Writing JSX is straightforward once you understand the rules. Here’s a simple example that includes a self-closing tag and the className attribute:

const MyComponent = () => {
  return (
    <div className="container">
      <h1>Hello, world!</h1>
      <p>This is a paragraph.</p>
      <br />

In this example, the MyComponent function returns a JSX element that represents a div containing an h1, a p, and a br tag. Note the use of className instead of class and the self-closing br tag.

Best Practices and Linting

Adhering to best practices can make your JSX code more readable, maintainable, and less prone to bugs. Here are some tips:

  1. Always Close Tags: As mentioned, JSX requires all elements to be closed. Even if you’re transitioning from HTML, make it a habit to close your JSX tags.
  2. Use CamelCase for Attributes: JSX uses camelCase for attributes like onClick and onChange, unlike the kebab-case (on-click, on-change) you might be used to in HTML.
  3. Keep Components Small: A component should ideally do one thing well. If it’s getting too large or handling too many tasks, consider breaking it into smaller, more manageable components.
  4. Linting: Tools like ESLint with plugins like eslint-plugin-react can enforce best practices and catch potential errors in your JSX code. If you’re using Create React App or Vite, ESLint is usually set up out of the box.
  "extends": ["eslint:recommended", "plugin:react/recommended"],
  "plugins": ["react"],
  "rules": {
    "react/jsx-uses-react": "error",
    "react/jsx-uses-vars": "error"

This ESLint configuration extends recommended rules from ESLint and the React plugin, ensuring that you’re following best practices.

Conclusion and Additional Resources

Summary of Key Takeaways

We’ve covered a lot of ground in this comprehensive guide, diving deep into the core aspects of React development. From understanding the one-way data flow model that makes React predictable and maintainable, to setting up your React projects using Create React App, Vite, or specialized frameworks like Next.js and Gatsby. We also demystified JSX, breaking down its rules and best practices to help you write cleaner, more efficient code.

  1. One-Way Data Flow: Mastering this concept will make your React apps more maintainable and easier to debug.
  2. Project Setup: Whether you’re a traditionalist using Create React App or looking for speed with Vite, knowing your setup options is crucial.
  3. JSX Rules: Understanding the nuances between JSX and HTML will save you from common pitfalls and make your development process smoother.

Additional Resources

  1. React Official Documentation: The best place to deepen your React knowledge.
  2. ESLint: A must-have tool for enforcing code quality and JSX best practices.
  3. React Patterns: Websites like React Patterns offer various design patterns and component structures that can be incredibly helpful.
  4. Community: Platforms like Stack Overflow, Reddit’s r/reactjs, and the Reactiflux Discord community are excellent for getting help and sharing knowledge.


Additional Tools and Libraries

  1. Redux: For state management beyond React’s built-in capabilities, Redux is the industry standard.
  2. React Router: For client-side routing, React Router is the most popular choice.
  3. Styled-components: For CSS-in-JS solutions, styled-components offer a lot of flexibility.


  1. How do I handle forms in React?
    • React offers controlled components to handle forms. You can manage the form data in the component’s state and update it using event handlers.
  2. What are hooks?
    • Hooks are functions that let you use state and lifecycle features in functional components. Common hooks include useState, useEffect, and useContext.
  3. How do I optimize performance?
    • React’s built-in useMemo and useCallback hooks can help prevent unnecessary renders. Additionally, tools like React DevTools can help you profile component performance.

Reach out if you want to join me and write articles with the nerds 🙂

© 2024 · Nerd Level Tech


Social Media

Stay connected on social media