009c60fbc3
Implements custom step creation forms and backend persistence: Task B.8 - StepForm Component: - Comprehensive form for creating custom steps - Step type selection (decision/action/solution) with descriptions - Required fields: title, instructions (markdown supported) - Optional fields: help text, commands (dynamic array), category, tags - Visibility control (private/team/public) - Save to library checkbox - Full validation with error display - Dynamic command management (add/remove, label + command) - Tag input with Enter key support Task B.9 - CustomStepModal: - Tabbed modal interface - Tab 1: "Type My Own" - embeds StepForm - Tab 2: "Browse Library" - embeds StepLibraryBrowser - Handles both saved steps (API) and drafts (no save) - Loading states during step creation - Error handling with user feedback - Returns Step or CustomStepDraft to parent Task B.10 - Backend Custom Steps Support: - Database migration: add custom_steps JSONB column to sessions - Updated Session model with custom_steps field - Updated SessionResponse schema with custom_steps - Updated SessionUpdate schema to accept custom_steps - Migration ready to run: 4cdb5cba1aff Task B.13 - Session Types Updates: - Added CustomStep and CustomStepDraft interfaces - Updated Session interface with custom_steps field - Updated SessionUpdate interface - Exported step types from types/index.ts - Full TypeScript support for custom step integration Remaining tasks: B.11 (TreeNavigationPage integration), B.12 (Export) Build tested successfully. 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...
},
},
])