- Moved n8n workflow schema to schemas/n8n-workflow.schema.json
- Added `variables` property at workflow root level for type-safe, reusable workflow configuration
- Implemented full variable system with:
* Type system (string, number, boolean, array, object, date, any)
* Validation rules (min, max, pattern, enum)
* Scope control (workflow, execution, global)
* Required/optional with default values
- Created comprehensive N8N_VARIABLES_GUIDE.md (6,800+ words) with:
* 5 real-world use case examples
* Best practices and migration guide from meta to variables
* Complete property reference and expression syntax
- Created N8N_VARIABLES_EXAMPLE.json demonstrating e-commerce order processing
- Documented schema gaps in N8N_SCHEMA_GAPS.md (10 missing enterprise features)
- Created migration infrastructure:
* scripts/migrate-workflows-to-n8n.ts for workflow format conversion
* npm scripts for dry-run and full migration
* N8N_COMPLIANCE_AUDIT.md tracking 72 workflows needing migration
- Established packagerepo backend workflows with n8n schema format
Impact: Variables now first-class citizens enabling DRY principle, type safety, and enterprise-grade configuration management across workflows.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add inline-flex and inline-grid to display enum for component definitions
- Create example component styles (Button, Card, Badge) for ui_home
- Validate example against enhanced styles_schema.json
- Created playwright.schema.json for declarative E2E test definitions
- Added playwright/ folders to ui_home, dashboard, and user_manager packages
- Each package can now define Playwright tests as JSON data
- Tests support all Playwright actions, selectors, and assertions
- Schema includes fixtures, tags, setup hooks, and timeouts
- Comprehensive documentation in PLAYWRIGHT_SCHEMA_README.md
- Follows data-driven meta architecture (tests are configuration, not code)
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Create page-config.schema.json - Validates route/page definitions
- Create workflow.schema.json - Validates workflow definitions
- Create credential.schema.json - Validates API credentials
- Create notification.schema.json - Validates notification templates
- Create component.schema.json - Validates component definitions
- Add README.md with usage examples and integration guides
These schemas:
- Ensure seed data is well-formed before database loading
- Can be used in VSCode for IDE autocompletion
- Integrate with validation tools and CI/CD pipelines
- Document required fields and valid values for each entity type
- Provide examples for each entity type
Schemas are in /schemas/seed-data/ alongside YAML entity definitions
in /dbal/shared/api/schema/entities/
This completes the foundation for proper seed data validation and
package organization.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Create /schemas/seed/ folder structure for seed data schemas
- Add page-config schema for PageConfig seed data
- Add component-config schema for ComponentConfig seed data
- Add workflow schema for Workflow seed data
- Add permission schema for permission seed data
- Update ui_home to reference schema location
- Added `jsonScript` property to metadata schema for JSON script entry points.
- Refactored `generate-package.ts` to replace Lua scripts with JSON scripts for lifecycle hooks.
- Updated test generation to use JSON format for metadata validation.
- Modified documentation and comments to reflect the transition from Lua to JSON scripting.
- Adjusted Storybook configuration and mock data to align with new JSON script structure.
- Renamed relevant files and references from Lua to JSON for consistency across the project.
- Introduced `edge-cases.params.json` to define parameter sets for various edge case scenarios including null handling, boundary values, empty collections, special characters, numeric overflow, concurrent access, and malformed data.
- Created `edge-cases.test.json` to implement parameterized tests for the defined edge cases, ensuring robust validation of edge case handling in the application.
- Added `test-parameters_schema.json` to establish a schema for defining parameterized test input parameters, enhancing validation and structure.
- Developed `tests_schema.json` to define the structure for parameterized unit tests, including setup, teardown, and test case definitions.
- Updated default schema version from 1.0.0 to 2.0.0 in config_schema.json, events_schema.json, forms_schema.json, jobs_schema.json, migrations_schema.json, and permissions_schema.json.
- Introduced storybook-common-definitions.json to centralize common definitions for storybook context and controls.
- Refactored storybook_schema.json to reference common definitions instead of duplicating schema properties.
- Enhanced test scripts for schema validation to ensure comprehensive coverage and improved error reporting.
- Introduced advanced validation functions in complex.json for order totals, shipping addresses, inventory checks, and credit card validation.
- Created settings.json for complete package configuration, including environment variables and feature flags.
- Added event handlers in handlers.json for user-related events such as creation, update, and deletion.
- Developed user registration and profile editing forms in user-form.json with validation rules.
- Implemented background jobs in tasks.json for user cleanup, daily digest emails, analytics processing, and database backups.
- Established initial database migrations in 001_initial.json for users and content tables.
- Defined role-based access control in rbac.json with roles, permissions, and policies.
- Created minimal package schemas with empty structures for API, components, config, entities, events, forms, jobs, migrations, permissions, scripts, styles, types, and validation.
- Created a new script `validate-all.sh` for automated validation of JSON schemas and example packages.
- Added a comprehensive README for TypeScript type definitions, detailing installation, usage examples, and advanced patterns.
- Introduced `generate-types.sh` to generate TypeScript definitions from JSON schemas using `json-schema-to-typescript` or `quicktype`.
- Implemented `metabuilder-schemas.d.ts` with hand-crafted TypeScript definitions for MetaBuilder schemas.
- Enhanced the structure and documentation of the TypeScript types to improve usability and clarity.
- Introduced QUICKSTART.md with security improvements, visual programming support, and cross-schema validation features.
- Updated entities_schema.json to remove deprecated 'primary' field.
- Enhanced index_schema.json with cross-validation rules and improved schema definitions.
- Created stdlib_schema.json for standard library functions and utilities.
- Updated validation_schema.json to include default regex patterns and sanitization options.
- Introduced a new JSON schema for package styles (styles_schema.json) defining design tokens and style properties.
- Removed the outdated types schema (types.schema.json) and replaced it with an updated version (types_schema.json) that includes enhanced type definitions and properties.
- Added a new validation schema (validation_schema.json) for JSON script validation functions, including reusable patterns and function definitions.
git
copilot-swe-agent[bot]