dataflow/ui
Paul Trowbridge 10dc92b45e Fix 'Mapping already exists' error on second save
After createMapping, the new mapping's id was not stored in allValues
state, so editing the row again fell into the create path instead of
update. Now stores created.id so subsequent saves correctly use updateMapping.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-05 20:50:40 -04:00
..
src Fix 'Mapping already exists' error on second save 2026-04-05 20:50:40 -04:00
.gitignore Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00
eslint.config.js Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00
index.html Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00
package.json Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00
README.md Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00
vite.config.js Add React UI and backend enhancements for dataflow 2026-03-29 00:35:33 -04:00

React + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the ESLint configuration

If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.