惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Microsoft Azure Blog
Microsoft Azure Blog
大猫的无限游戏
大猫的无限游戏
月光博客
月光博客
V
V2EX
PCI Perspectives
PCI Perspectives
Latest news
Latest news
博客园 - 三生石上(FineUI控件)
C
CERT Recently Published Vulnerability Notes
W
WeLiveSecurity
Last Week in AI
Last Week in AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
P
Palo Alto Networks Blog
T
The Exploit Database - CXSecurity.com
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
WordPress大学
WordPress大学
V
Vulnerabilities – Threatpost
H
Heimdal Security Blog
Attack and Defense Labs
Attack and Defense Labs
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Hacker News: Ask HN
Hacker News: Ask HN
博客园 - 叶小钗
V
Visual Studio Blog
Jina AI
Jina AI
P
Proofpoint News Feed
罗磊的独立博客
SecWiki News
SecWiki News
J
Java Code Geeks
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
L
LINUX DO - 热门话题
Security Archives - TechRepublic
Security Archives - TechRepublic
The Hacker News
The Hacker News
Hugging Face - Blog
Hugging Face - Blog
N
News and Events Feed by Topic
NISL@THU
NISL@THU
T
Tailwind CSS Blog
T
Tenable Blog
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Recent Announcements
Recent Announcements
H
Hacker News: Front Page
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
T
Tor Project blog
宝玉的分享
宝玉的分享
Help Net Security
Help Net Security
S
Security Affairs
Microsoft Security Blog
Microsoft Security Blog
Google DeepMind News
Google DeepMind News
F
Fortinet All Blogs
G
GRAHAM CLULEY

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Creating Dynamic Lists in React: A Step-by-Step Guide
Amirah Nasih · 2026-05-17 · via DEV Community

Creating Dynamic Lists in React: A Step-by-Step Guide

Lists in React are similar to lists in JavaScript. They are commonly used to display menus or a list of items on a website. To use lists in React, we need to use a unique key attribute for each item in the list. This is important because it helps React identify which items have been changed, updated or removed.

Hey there friends! It's been a minute since I last posted on this platform, but I'm back and ready to dive into the world of React once again. Let's get started!

To create a list in React, it is best to create a new component specifically for the list. This component will take in the list data through props. Inside the component, we can use the map function to iterate through the list and display each item.

For the sake of simplicity and learning, this article will give a simple example of creating a list of posts, where the key is "id" of the post, and the "title" and "body" of the post is displayed. The final output of the tutorial is shown in an embedded code editor. It's recommended to follow this tutorial and practice it several times to better understand the concepts.

Code Output

You will get this result once you have finished the tutorial.

Edit list-and-keys

Getting Started

To begin, you can create react app using the command line or any code editor (e.g., VSCode). You can also directly use the CodeSandbox for an online code editor that is simple to use and allows you to deploy your code.

What Components Needed

First, we need to understand what components are required to display a list of blog posts using React. You will need to create at least the following components:

  1. A component that retrieves the blog post data from a source, a Parent component - (App.js).

  2. A component that renders the list of blog posts, a Child component - (BlogList.js).

  3. A reusable component that can be reused in other parts of the application where you want to display a single blog post, an Inner Child Component - (BlogCard.js).

You can create these components as separate JavaScript files and import them into your main application file, where you can use them to build out the list of blog posts.

Data Retrieving Component

  1. App.js - This component would handle retrieving the blog post data from any source. For the sake of simplicity, we will just have a simple array of objects [{key:value}, {key:value}] and that is the const posts. Inside them, we have the id, title, and body.

We will import the BlogList component into the App component and pass the posts data through props because we want to use the posts data to be displayed in the BlogList.

App.js

import BlogList from "./components/BlogList";

export default function App() {
    const posts = [
        {
            id: 1,
            title: "buildspace web3 demo showcase!",
            body:
                "Last night's buildspace demo day was a blast, as was go-karting around the map on gather.town dressed as a pumpkin. It's a massive web3 display! Over…"
        },
        {
            id: 2,
            title: "ReactJS - Introduction",
            body:
                "What is ReactJS? ➡️declarative, efficient, and flexible JavaScript library for building reusable UI components. ➡️an open-source, component-based…"
        },
        {
            id: 3,
            title: "Build Metaverse with Gather.Town for Free",
            body:
                "Gather.Town Looking for more interactive web-conferencing software like Zoom, but with more fun virtual interactions just like in real life. Then, you…"
        }
    ];

    return (
        <div>
            <BlogList posts={posts} />
        </div>
    );
}

Enter fullscreen mode Exit fullscreen mode

Display the Lists Component

  1. BlogList.js - This component would render the list of blog posts using the data retrieved by the Appcomponent and display all the posts on our screen browser.

Inside the BlogList functional component, it will take props.

import BlogCard from "./BlogCard";

const BlogList = (props) => {
    const content = props.posts.map((post) => {
        return <BlogCard key={post.id} props={post} />;
    });

    return (
        <div>
            <h1>My Posts</h1>
            <div>{content}</div>
        </div>
    );
};

export default BlogList;

Enter fullscreen mode Exit fullscreen mode

This code is a React component named BlogList which maps over an array of blog posts (props.posts) and returns an array of BlogCard components. Each BlogCard component is rendered with a unique key prop (post.id) and passed the whole post data as props (props={post}).

Let's go line-by-line through the code:

  1. import BlogCard from "./BlogCard": This line imports a component called BlogCard from another file called BlogCard.js in the same directory.

  2. const BlogList = (props) => {...}: This line creates a new component called BlogList using a special type of function called an arrow function. This component will receive data from outside the component through its props argument.

  3. const content = props.posts.map((post) => {: This line creates a new constant called content which will contain an array of components created by mapping over the posts array received through props. It maps through an array of posts stored in props and creates a new array of BlogCard components for each post where it will return a component for each post. "Mapping through an array" means iterating/looping over the elements of an array and performing a specific operation on each element.

  4. return <BlogCard key={post.id} props={post} />;: This line returns a new component of type BlogCard for each post in the posts array. The component will receive data through its props argument and will have a key property set to the id of the current post. Remember to use lists in React, we need to have a unique key attribute for each item in the list. Otherwise, a warning will appear.

  5. <div>{content}</div>: This line returns a div element that contains all the BlogCard components created in the previous step. Which embeds the mapped array of BlogCard components into a div element.

  6. <h1>My Posts</h1>: This line displays a header element with the text "My Posts".

  7. <div>...</div>: This line wraps the header and the content div in a parent div.

  8. export default BlogList;: This line exports the BlogList component so that it can be used in other files.

The overall logic of this code is to create a component BlogList that displays a list of blog posts using the BlogCard component. The component receives data about the posts through its props argument, maps over the posts array to create an array of BlogCard components, and displays these components in a div along with a header.

Reusable Component

  1. BlogCard.js - This component would be a reusable component that takes a single blog post as a prop and displays the details of the blog post in a card format. This component can be reused in other parts of the application where you want to display a single blog post.

This component uses destructuring assignment to extract the "id", "title", and "body" properties from the props object.

This component in React is called "BlogCard". It takes in a prop called "props", which contains information about a blog post. The component then uses destructuring assignment to extract the "id", "title", and "body" properties from the props object.

The component then returns a JSX element that displays the post information in a specific format. The id of the post is displayed first, followed by its title, and then its body content.

const BlogCard = ({ props }) => {
    const { id, title, body } = props;

    return (
        <div>
            <h2>
                {id}. {title}
            </h2>
            <p>{body}</p>
        </div>
    );
};

export default BlogCard;

Enter fullscreen mode Exit fullscreen mode

Let's go through line-by-line:

  1. const BlogCard = ({ props }) => {...}: This line creates a new component called BlogCard using an arrow function. This component will receive data from outside the component through its props argument.

  2. const { id, title, body } = props;: This line uses destructuring to extract the id, title, and body properties from the props object.

  3. <h2>{id}. {title}</h2>: This line returns a header element with the id and title properties from the props object.

  4. <p>{body}</p>: This line returns a paragraph element with the body property from the props object.

  5. <div>...</div>: This line wraps the header and paragraph elements in a parent div.

  6. export default BlogCard;: This line exports the BlogCard component so it can be used in other files.

The overall logic of this code is to create a component BlogCard that displays a single blog post. The component receives data about the post through its props argument and displays the post's id, title, and body properties in a header and a paragraph element.

Destructuring

Destructuring is a feature in JavaScript that allows you to extract data from arrays or objects and assign them to variables. The main purpose of destructuring is to make it easier and more convenient to access the properties and values of an object or array.

// First code snippet
const BlogList = (props) => {

// vs

// Second code snippet
const BlogCard = ({ props }) => {

Enter fullscreen mode Exit fullscreen mode

What is the difference between these two? Why are props inside the BlogList not destructured?

The difference between these two code snippets is that in the first code snippet, props is passed to the BlogList component as a single argument, and in the second code snippet, props is destructured from the props object passed to the BlogCard component.

  1. First code snippet - props is an object that contains all of the properties that are passed to the BlogList component. In this case, it is not necessary to destruct the props object, as the code only needs to access one property, posts.

  2. Second code snippet - props is destructured from the props object, allowing for the properties id, title, and body to be accessed directly. This reduces the need to access properties through the props object and makes the code more readable and maintainable.

In short, the difference is in the way that the properties are accessed within the component. The first code snippet accesses the properties through the props object, while the second code snippet accesses the properties directly by destructuring the props object.

Full Code

App.js

import BlogList from "./components/BlogList";

export default function App() {
    const posts = [
        {
            id: 1,
            title: "buildspace web3 demo showcase!",
            body:
                "Last night's buildspace demo day was a blast, as was go-karting around the map on gather.town dressed as a pumpkin. It's a massive web3 display! Over…"
        },
        {
            id: 2,
            title: "ReactJS - Introduction",
            body:
                "What is ReactJS? ➡️declarative, efficient, and flexible JavaScript library for building reusable UI components. ➡️an open-source, component-based…"
        },
        {
            id: 3,
            title: "Build Metaverse with Gather.Town for Free",
            body:
                "Gather.Town Looking for more interactive web-conferencing software like Zoom, but with more fun virtual interactions just like in real life. Then, you…"
        }
    ];

    return (
        <div>
            <BlogList posts={posts} />
        </div>
    );
}

Enter fullscreen mode Exit fullscreen mode

BlogList.js

import BlogCard from "./BlogCard";

const BlogList = (props) => {
    const content = props.posts.map((post) => {
        return <BlogCard key={post.id} props={post} />;
    });

    return (
        <div>
            <h1>My Posts</h1>
            <div>{content}</div>
        </div>
    );
};

export default BlogList;

Enter fullscreen mode Exit fullscreen mode

BlogCard.js

const BlogCard = ({ props }) => {
    const { id, title, body } = props;

    return (
        <div>
            <h2>
                {id}. {title}
            </h2>
            <p>{body}</p>
        </div>
    );
};

export default BlogCard;

Enter fullscreen mode Exit fullscreen mode


👉 Please share my posts with the community at daily.dev / social media by adding the article's URL to the feed. By adding my article's URL to the feed, I can share my insights and knowledge with other tech enthusiasts and contribute to the passionate community.

Cheers✨

Thank you for your continued support and for sticking around even though I've been away for a bit. I've been busy with some exciting projects, but I'm thrilled to be back and writing again!