


Introduction
Yay! ? You've made it to the final part of this two-part series! If you haven't already checked out Part 1, stop right here and go through that first. Don't worry, we'll wait until you’re back! ?
In Part 1, we built the CustomTable component. You can see it in action here.
In this second part, we’ll be extending the component to add some new features. Here's what we'll be working towards:
To support this, the CustomTable component will need some enhancements:
- The ability to format the rendered value—e.g., rendering a number with proper formatting.
- Flexibility to allow users to provide custom templates for rendering rows, giving them control over how each column is displayed.
Let's dive into building the first feature.
Extending the Column Interface
We’ll start by adding a format method to the Column interface to control how specific columns render their values.
interface Column<t> { id: keyof T; label: string; format?: (value: string | number) => string; } </t>
This optional format method will be used to format data when necessary. Let’s see how this works with an example from the Country.tsx file. We’ll add a format method to the population column.
const columns: Column<country>[] = [ { id: "name", label: "Name" }, { id: "code", label: "ISO\u00a0Code" }, { id: "population", label: "Population", format: (value) => new Intl.NumberFormat("en-US").format(value as number), }, { id: "size", label: "Size\u00a0(km\u00b2)", }, { id: "density", label: "Density", }, ]; </country>
Here, we’re using the JavaScript Intl.NumberFormat method to format the population as a number. You can learn more about this method here.
Next, we need to update our CustomTable component to check for the format function and apply it when it exists.
<tablebody> {rows.map((row, index) => ( <tablerow hover tabindex="{-1}" key="{index}"> {columns.map((column, index) => ( <tablecell key="{index}"> {column.format ? column.format(row[column.id] as string) : (row[column.id] as string)} </tablecell> ))} </tablerow> ))} </tablebody>
With this modification, the population column now renders with the appropriate formatting. You can see it in action here.
Supporting Custom Templates
Now, let's implement the next feature: allowing custom templates for rendering columns. To do this, we’ll add support for passing JSX as a children prop or using render props, giving consumers full control over how each cell is rendered.
First, we’ll extend the Props interface to include an optional children prop.
interface Props<t> { rows: T[]; columns: Column<t>[]; children?: (row: T, column: Column<t>) => React.ReactNode; } </t></t></t>
Next, we’ll modify our CustomTable component to support this new prop while preserving the existing behavior.
<tablerow> {columns.map((column, index) => ( <tablecell key="{index}"> {children ? children(row, column) : column.format ? column.format(row[column.id] as string) : row[column.id]} </tablecell> ))} </tablerow>
This ensures that if the children prop is passed, the custom template is used; otherwise, we fall back to the default behavior.
Let’s also refactor the code to make it more reusable:
const getFormattedValue = (column, row) => { const value = row[column.id]; return column.format ? column.format(value) : value as string; }; const getRowTemplate = (row, column, children) => { return children ? children(row, column) : getFormattedValue(column, row); };
Custom Row Component
Now let’s build a custom row component in the Countries.tsx file. We’ll create a CustomRow component to handle special rendering logic.
interface RowProps { row: Country; column: Column<country>; } const CustomRow = ({ row, column }: RowProps) => { const value = row[column.id]; if (column.format) { return <span>{column.format(value as string)}</span>; } return <span>{value}</span>; }; </country>
Then, we’ll update Countries.tsx to pass this CustomRow component to CustomTable.
const Countries = () => ( <customtable columns="{columns}" rows="{rows}"> {(row, column) => <customrow column="{column}" row="{row}"></customrow>} </customtable> );
For People.tsx, which doesn’t need any special templates, we can simply render the table without the children prop.
const People = () => <customtable columns="{columns}" rows="{rows}"></customtable>;
Improvements
One improvement we can make is the use of array indexes as keys, which can cause issues. Instead, let’s enforce the use of a unique rowKey for each row.
We’ll extend the Props interface to require a rowKey.
interface Props<t> { rowKey: keyof T; rows: T[]; columns: Column<t>[]; children?: (row: T, column: Column<t>) => React.JSX.Element | string; onRowClick?: (row: T) => void; } </t></t></t>
Now, each consumer of CustomTable must provide a rowKey to ensure stable rendering.
<customtable rowkey="code" rows="{rows}" onrowclick="{handleRowClick}" columns="{columns}"> {(row, column) => <customrow column="{column}" row="{row}"></customrow>} </customtable>
Final Code
Check out the full code here.
Conclusion
In this article, we extended our custom CustomTable component by adding formatting options and the ability to pass custom templates for columns. These features give us greater control over how data is rendered in tables, while also making the component flexible and reusable for different use cases.
We also improved the component by enforcing a rowKey prop to avoid using array indexes as keys, ensuring more efficient and stable rendering.
I hope you found this guide helpful! Feel free to share your thoughts in the comments section.
Thanks for sticking with me through this journey! ?
The above is the detailed content of How to create a custom table component with React and Typescript (Part 2). For more information, please follow other related articles on the PHP Chinese website!

JavaScript core data types are consistent in browsers and Node.js, but are handled differently from the extra types. 1) The global object is window in the browser and global in Node.js. 2) Node.js' unique Buffer object, used to process binary data. 3) There are also differences in performance and time processing, and the code needs to be adjusted according to the environment.

JavaScriptusestwotypesofcomments:single-line(//)andmulti-line(//).1)Use//forquicknotesorsingle-lineexplanations.2)Use//forlongerexplanationsorcommentingoutblocksofcode.Commentsshouldexplainthe'why',notthe'what',andbeplacedabovetherelevantcodeforclari

The main difference between Python and JavaScript is the type system and application scenarios. 1. Python uses dynamic types, suitable for scientific computing and data analysis. 2. JavaScript adopts weak types and is widely used in front-end and full-stack development. The two have their own advantages in asynchronous programming and performance optimization, and should be decided according to project requirements when choosing.

Whether to choose Python or JavaScript depends on the project type: 1) Choose Python for data science and automation tasks; 2) Choose JavaScript for front-end and full-stack development. Python is favored for its powerful library in data processing and automation, while JavaScript is indispensable for its advantages in web interaction and full-stack development.

Python and JavaScript each have their own advantages, and the choice depends on project needs and personal preferences. 1. Python is easy to learn, with concise syntax, suitable for data science and back-end development, but has a slow execution speed. 2. JavaScript is everywhere in front-end development and has strong asynchronous programming capabilities. Node.js makes it suitable for full-stack development, but the syntax may be complex and error-prone.

JavaScriptisnotbuiltonCorC ;it'saninterpretedlanguagethatrunsonenginesoftenwritteninC .1)JavaScriptwasdesignedasalightweight,interpretedlanguageforwebbrowsers.2)EnginesevolvedfromsimpleinterpreterstoJITcompilers,typicallyinC ,improvingperformance.

JavaScript can be used for front-end and back-end development. The front-end enhances the user experience through DOM operations, and the back-end handles server tasks through Node.js. 1. Front-end example: Change the content of the web page text. 2. Backend example: Create a Node.js server.

Choosing Python or JavaScript should be based on career development, learning curve and ecosystem: 1) Career development: Python is suitable for data science and back-end development, while JavaScript is suitable for front-end and full-stack development. 2) Learning curve: Python syntax is concise and suitable for beginners; JavaScript syntax is flexible. 3) Ecosystem: Python has rich scientific computing libraries, and JavaScript has a powerful front-end framework.


Hot AI Tools

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

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

Undress AI Tool
Undress images for free

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

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

Zend Studio 13.0.1
Powerful PHP integrated development environment

Safe Exam Browser
Safe Exam Browser is a secure browser environment for taking online exams securely. This software turns any computer into a secure workstation. It controls access to any utility and prevents students from using unauthorized resources.

SublimeText3 English version
Recommended: Win version, supports code prompts!

PhpStorm Mac version
The latest (2018.2.1) professional PHP integrated development tool
