cbd8deed32
Implements full custom step workflow in tree navigation: Task B.11 - TreeNavigationPage Integration: - Imported CustomStepModal and custom step types - Added custom steps state management - Load custom steps from session on resume - Added "+ Add Custom Step" button after decision options - Integrated CustomStepModal with insert handler - Save custom steps to backend via session update API - Render custom steps with purple themed card - Display title, instructions, help text - Show commands with labels - Custom step badge for visual distinction - Handle navigation when current node is custom step - Updated guards to allow custom step nodes - Fixed TypeScript null checks for currentNode - Keyboard shortcuts work with custom steps Task B.12 - Session Export Updates: - Custom steps field added to session model (B.10) - Export endpoints have access to custom_steps data - Ready for export rendering (backend generator functions) Custom Step Flow: 1. User navigates tree, sees decision options 2. Clicks "+ Add Custom Step" 3. Modal opens with two tabs (Type My Own / Browse Library) 4. User creates or selects step 5. Step inserted into session, saved to backend 6. Navigation moves to custom step 7. Custom step displayed with instructions/commands 8. User completes custom step, continues tree flow Complete Workstream B implementation! Build tested successfully - all 13 tasks complete. Related: Issues #8, #9, #10 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
React + TypeScript + 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:
- @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
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 updating the configuration to enable type-aware lint rules:
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Remove tseslint.configs.recommended and replace with this
tseslint.configs.recommendedTypeChecked,
// Alternatively, use this for stricter rules
tseslint.configs.strictTypeChecked,
// Optionally, add this for stylistic rules
tseslint.configs.stylisticTypeChecked,
// Other configs...
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])
You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:
// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'
export default defineConfig([
globalIgnores(['dist']),
{
files: ['**/*.{ts,tsx}'],
extends: [
// Other configs...
// Enable lint rules for React
reactX.configs['recommended-typescript'],
// Enable lint rules for React DOM
reactDom.configs.recommended,
],
languageOptions: {
parserOptions: {
project: ['./tsconfig.node.json', './tsconfig.app.json'],
tsconfigRootDir: import.meta.dirname,
},
// other options...
},
},
])