Introduction
Today, I'll share how I built a polished food database management system using modern React patterns. We'll focus on creating a responsive data table with seamless optimistic updates, combining the power of TanStack Query (formerly React Query) with Mantine's component library.
Project Overview
Requirements
- Display food items in a data table
- Add new items with immediate feedback
- Handle loading and error states gracefully
- Provide smooth optimistic updates
Tech Stack
- TanStack Query: Server state management
- Mantine UI: Component library and form management
- Mantine React Table: Advanced table functionality
- Wretch: Clean API calls
- TypeScript: Type safety
Implementation Guide
1. Setting Up the Foundation
First, let's define our types and API configuration:
// Types export type GetAllFoods = { id: number; name: string; category: string; }; export type CreateNewFoodType = Pick< GetAllFoods, | 'name' | 'category' >; // API Configuration export const API = wretch('<http://localhost:9999>').options({ credentials: 'include', mode: 'cors', headers: { 'Content-Type': 'application/json', Accept: 'application/json', }, }); // TANSTACK QUERY export const getFoodOptions = () => { return queryOptions({ queryKey: ['all-foods'], queryFn: async () => { try { return await API.get('/foods') .unauthorized(() => { console.log('Unauthorized'); }) .json<Array<GetAllFoods>>(); } catch (e) { console.log({ e }); throw e; } }, }); }; export const useGetAllFoods = () => { return useQuery({ ...getFoodOptions(), }); };
2. Building the Data Table
The table component using Mantine React Table:
const FoodsView = () => { const { data } = useGetAllFoods(); const columns = useMemo<MRT_ColumnDef<GetAllFoods>[]>( () => [ { accessorKey: 'id', header: 'ID', }, { accessorKey: 'name', header: 'Name', }, { accessorKey: 'category', header: 'Category', }, // ... other columns ], [] ); const table = useMantineReactTable({ columns, data: data ?? [], // Optimistic update animation mantineTableBodyCellProps: ({ row }) => ({ style: row.original.id < 0 ? { animation: 'shimmer-and-pulse 2s infinite', background: `linear-gradient( 110deg, transparent 33%, rgba(83, 109, 254, 0.2) 50%, transparent 67% )`, backgroundSize: '200% 100%', position: 'relative', } : undefined, }), }); return <MantineReactTable table={table} />; };
3. Creating the Form
A form component for adding new foods:
const CreateNewFood = () => { const { mutate } = useCreateNewFood(); const formInputs = [ { name: 'name', type: 'text' }, { name: 'category', type: 'text' }, ]; const form = useForm<CreateNewFoodType>({ initialValues: { name: '', category: '', // ... other fields }, }); return ( <Box mt="md"> <form onSubmit={form.onSubmit((data) => mutate(data))}> <Flex direction="column" gap="xs"> {formInputs.map((input) => ( <TextInput key={input.name} {...form.getInputProps(input.name)} label={input.name} tt="uppercase" type={input.type} /> ))} <Button type="submit" mt="md"> Create New </Button> </Flex> </form> </Box> ); };
4. Implementing Optimistic Updates
The heart of our implementation - TanStack Query mutation with optimistic updates:
export const useCreateNewFood = () => { const queryClient = useQueryClient(); return useMutation({ mutationKey: ['create-new-food'], mutationFn: async (data: CreateNewFoodType) => { await new Promise(resolve => setTimeout(resolve, 3000)); // Demo delay return API.url('/foods').post(data).json<GetAllFoods>(); }, onMutate: async (newFood) => { // Cancel in-flight queries await queryClient.cancelQueries({ queryKey: ['all-foods'] }); // Snapshot current state const previousFoods = queryClient.getQueryData<GetAllFoods[]>(['all-foods']); // Create optimistic entry const optimisticFood: GetAllFoods = { id: -Math.random(), ...newFood, verified: false, createdBy: 0, createdAt: new Date().toISOString(), updatedAt: new Date().toISOString(), }; // Update cache optimistically queryClient.setQueryData(['all-foods'], (old) => old ? [...old, optimisticFood] : [optimisticFood] ); return { previousFoods }; }, onError: (err, _, context) => { // Rollback on error if (context?.previousFoods) { queryClient.setQueryData(['all-foods'], context.previousFoods); } }, onSettled: () => { // Refetch to ensure consistency queryClient.invalidateQueries({ queryKey: ['all-foods'] }); }, }); };
5. Animation Styles
The animation that brings our optimistic updates to life:
@keyframes shimmer-and-pulse { 0% { background-position: 200% 0; transform: scale(1); box-shadow: 0 0 0 0 rgba(83, 109, 254, 0.2); } 50% { background-position: -200% 0; transform: scale(1.02); box-shadow: 0 0 0 10px rgba(83, 109, 254, 0); } 100% { background-position: 200% 0; transform: scale(1); box-shadow: 0 0 0 0 rgba(83, 109, 254, 0); } }
Best Practices
-
Optimistic Updates
- Immediately update UI for better UX
- Handle error cases with rollbacks
- Maintain data consistency with proper invalidation
-
Type Safety
- Use TypeScript for better maintainability
- Define clear interfaces for data structures
- Leverage type inference where possible
-
Performance
- Cancel in-flight queries during updates
- Use proper query invalidation
- Implement efficient form state management
-
User Experience
- Provide immediate feedback
- Show loading states
- Handle errors gracefully
Future Enhancements
Consider these improvements for your implementation:
- Undo/redo functionality
- Form validation rules
- Error boundary implementation
Results
Once Completed Request
Conclusion
This implementation demonstrates how to create a robust data management system using modern React patterns. The combination of TanStack Query, Mantine UI, and thoughtful optimistic updates creates a smooth and professional user experience.
Remember to:
- Keep your components focused and maintainable
- Handle all possible states (loading, error, success)
- Use TypeScript for better code quality
- Consider user experience in your implementation
What challenges have you faced implementing optimistic updates in your React applications? Share your experiences in the comments below.
The above is the detailed content of Building a Data Table with Optimistic Updates. 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

Java and JavaScript are different programming languages, each suitable for different application scenarios. Java is used for large enterprise and mobile application development, while JavaScript is mainly used for web page development.

The following points should be noted when processing dates and time in JavaScript: 1. There are many ways to create Date objects. It is recommended to use ISO format strings to ensure compatibility; 2. Get and set time information can be obtained and set methods, and note that the month starts from 0; 3. Manually formatting dates requires strings, and third-party libraries can also be used; 4. It is recommended to use libraries that support time zones, such as Luxon. Mastering these key points can effectively avoid common mistakes.

PlacingtagsatthebottomofablogpostorwebpageservespracticalpurposesforSEO,userexperience,anddesign.1.IthelpswithSEObyallowingsearchenginestoaccesskeyword-relevanttagswithoutclutteringthemaincontent.2.Itimprovesuserexperiencebykeepingthefocusonthearticl

JavaScriptispreferredforwebdevelopment,whileJavaisbetterforlarge-scalebackendsystemsandAndroidapps.1)JavaScriptexcelsincreatinginteractivewebexperienceswithitsdynamicnatureandDOMmanipulation.2)Javaoffersstrongtypingandobject-orientedfeatures,idealfor

Event capture and bubble are two stages of event propagation in DOM. Capture is from the top layer to the target element, and bubble is from the target element to the top layer. 1. Event capture is implemented by setting the useCapture parameter of addEventListener to true; 2. Event bubble is the default behavior, useCapture is set to false or omitted; 3. Event propagation can be used to prevent event propagation; 4. Event bubbling supports event delegation to improve dynamic content processing efficiency; 5. Capture can be used to intercept events in advance, such as logging or error processing. Understanding these two phases helps to accurately control the timing and how JavaScript responds to user operations.

JavaScripthassevenfundamentaldatatypes:number,string,boolean,undefined,null,object,andsymbol.1)Numbersuseadouble-precisionformat,usefulforwidevaluerangesbutbecautiouswithfloating-pointarithmetic.2)Stringsareimmutable,useefficientconcatenationmethodsf

If JavaScript applications load slowly and have poor performance, the problem is that the payload is too large. Solutions include: 1. Use code splitting (CodeSplitting), split the large bundle into multiple small files through React.lazy() or build tools, and load it as needed to reduce the first download; 2. Remove unused code (TreeShaking), use the ES6 module mechanism to clear "dead code" to ensure that the introduced libraries support this feature; 3. Compress and merge resource files, enable Gzip/Brotli and Terser to compress JS, reasonably merge files and optimize static resources; 4. Replace heavy-duty dependencies and choose lightweight libraries such as day.js and fetch

The main difference between ES module and CommonJS is the loading method and usage scenario. 1.CommonJS is synchronously loaded, suitable for Node.js server-side environment; 2.ES module is asynchronously loaded, suitable for network environments such as browsers; 3. Syntax, ES module uses import/export and must be located in the top-level scope, while CommonJS uses require/module.exports, which can be called dynamically at runtime; 4.CommonJS is widely used in old versions of Node.js and libraries that rely on it such as Express, while ES modules are suitable for modern front-end frameworks and Node.jsv14; 5. Although it can be mixed, it can easily cause problems.
