- 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
- Moved auth tests: packages/auth → packages/ui_auth
- Moved CRUD tests: packages/crud → packages/user_manager
- Moved package tests: packages/package_tests → packages/package_manager
- Moved pagination tests: packages/pagination → packages/data_table
- Merged navigation tests into packages/ui_home (navigation belongs to home page)
- Removed standalone test packages (crud, auth, package_tests, navigation, pagination)
- Tests now properly belong to the functional packages they test
- Updated TEST_STORY_CONVERSION.md with final package mapping
- api_tests and smoke_tests remain as cross-cutting integration test packages
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- 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 FAKEMUI_REGISTRY mapping all 131+ fakemui components (form, display, layout, navigation, modal, table, icons, feedback, advanced)
- Update JSON renderer to use fakemui by default
- Add component category mapping for easier lookup
- Create example component definitions in ui_home package demonstrating fakemui integration
- Add comprehensive FAKEMUI_INTEGRATION.md guide with component inventory, template syntax, usage patterns, and best practices
- Add COMPONENT_MAPPING.md documenting all available components and integration status
This enables fully declarative JSON-based UI components rendered with Material Design fakemui library, allowing non-code customization of all UI elements.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Move all seed data from packages/*/seed/ to packages/*/[entity-type]/
- Establish clear entity-type folder structure (page-config, workflow, etc.)
- Update metadata.json files to be entity-specific, not package-level
- Reorganize all 12 bootstrap packages to new structure:
- ui_home, ui_header, ui_footer, ui_auth, ui_login
- dashboard, user_manager, role_editor, admin_dialog
- package_manager, database_manager, schema_editor
Update seed orchestration in /dbal/development/src/seeds/index.ts:
- Look for packages/[packageId]/page-config/ folders instead of seed/
- Load all JSON files in entity folders (not just specific references)
- Maintains idempotency and error handling
Update documentation:
- CLAUDE.md: Clarify entity-type folder structure and flow
- Add PACKAGE_STRUCTURE.md: Complete guide for organizing packages
- Update Task 2 with step-by-step entity folder setup
Benefits:
- Clear navigation: instantly see what each package provides
- Prevents AI from overthinking: structure is obvious
- One folder per entity type: simple and consistent
- Scalable: easy to add new entity types
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
Fixes ui_home package to comply with metadata_schema.json:
Root package.json changes:
- Added reference for validation
- Moved minLevel from 1 to 0 (public package, not level 1 only)
- Added repository, homepage, bugs URLs
- Added keywords for discoverability
- Fixed dependencies version constraints (^1.0.0 instead of *)
- Fixed exports structure (removed non-existent 'pages' property)
- Fixed seed property to reference page-config.json file
- Fixed tests property structure (scripts not suites)
Seed metadata.json changes:
- Added reference
- Now serves as seed index/manifest
- References page-config.json for PageConfig seed data
- Added license and keywords
New file:
- seed/page-config.json - Contains actual PageConfig entries for database
seedDatabase() function updates:
- Now reads seed/metadata.json.seed.schema property for file reference
- Loads PageConfig entries from seed/page-config.json
- Properly maps all PageConfig fields from seed data
- Handles optional fields gracefully with defaults
Result: ui_home package now fully complies with metadata_schema.json
and properly separates package definition from seed data.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add CLAUDE.md: AI assistant instructions for MetaBuilder project architecture
- Add TESTING.md: Comprehensive E2E testing guide and troubleshooting
Core changes:
- Create Playwright global.setup.ts to seed database before E2E tests
- Add /api/setup endpoint to trigger database seeding via HTTP
- Implement seed-home-page.ts module loaded from ui_home package metadata
- Create ui_home/seed/metadata.json defining home page PageConfig seed data
Architecture established:
- Packages define seed data in seed/metadata.json
- Seed functions are idempotent (check before creating)
- Global setup calls /api/setup before running tests
- Database schema must be created via 'npm run db:push' before seeding
Test flow:
1. Playwright starts webServer (generates Prisma client, starts Next.js)
2. Global setup waits for server, calls POST /api/setup
3. Seeding creates default data from packages
4. E2E tests run against seeded database
This establishes proper separation of concerns:
- DBAL adapter for database access (not raw Prisma)
- Package-driven seed data (not hardcoded in code)
- HTTP endpoint for explicit database initialization
- Idempotent seeds (safe to rerun)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- 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.
- Updated functions.json files in theme_editor, ui_auth, ui_footer, ui_header, ui_home, ui_intro, ui_level2, ui_level3, ui_level4, ui_level5, ui_level6, ui_login, ui_pages, ui_permissions, user_manager, and workflow_editor packages.
- Removed luaScript entries from function definitions, retaining only category and other relevant metadata.
- Adjusted documentation in prisma/README.md to remove LuaScript entity reference.
- Changed devDependencies from "lua_test" to "testing" in package.json for ui_level4, ui_level5, ui_level6, ui_login, ui_pages, ui_permissions, user_manager, and workflow_editor.
- Removed legacy test scripts and parameterized tests, replacing them with a unified test suite structure in the tests section of package.json.
- Introduced new metadata.params.json files for each package to define test parameters for package ID validation, icon file existence, and JSON schema validation.
- Created new metadata.test.json files for each package to define structured test cases for validating package metadata, including checks for package ID, icon file existence, and schema validity.
- Updated action names from "moderate", "write", "configure", and "ban" to "manage", "update", and "execute" across multiple roles in the forum_forge, github_tools, irc_webchat, json_script_example, lua_test, media_center, nav_menu, package_validator, quick_guide, role_editor, schema_editor, screenshot_analyzer, smtp_config, social_hub, stats_grid, stream_cast, ui_auth, ui_footer, ui_header, ui_home, ui_intro, ui_level2, ui_level3, ui_level4, ui_level5, ui_level6, ui_login, ui_pages, and ui_permissions packages.
- Changed resource types from "content", "data", "ui", "config", and "external" to "custom", "entity", and "component" for better clarity and consistency.
- Adjusted actions in roles to reflect new naming conventions and improve readability.
- Created package.json for ui_pages with dependencies and exports.
- Added roles.json for access permissions related to UI pages.
- Implemented functions.json for managing UI pages and routing.
- Developed stories.json for Storybook showcasing UI pages components.
- Defined styles tokens for UI pages including colors, spacing, and typography.
feat(ui_permissions): Introduce UI Permissions package for access control
- Created package.json for ui_permissions with permission utilities.
- Added roles.json defining permissions for a 6-level access control system.
- Implemented functions.json for permission checking and level management.
- Developed stories.json for Storybook showcasing permission-related components.
- Defined styles tokens for UI permissions including colors and spacing.
- Added type annotations and class definitions in the dashboard layout, stats, and data table modules for improved type safety and documentation.
- Introduced new classes for UI components, props, and configuration in the form builder, navigation menu, notification center, and UI dialogs packages.
- Implemented detailed type definitions for actions, fields, and pagination components to streamline usage and enhance clarity.
- Updated initialization functions in multiple packages to include versioning and installation context.
- Improved structure and readability of the codebase by organizing and documenting component properties and methods.
- Deleted existing metadata test files for stream_cast, ui_auth, ui_dialogs, ui_footer, ui_header, ui_home, ui_intro, ui_level2, ui_level3, ui_level4, and ui_level5 packages.
- Introduced new Lua-based component validation tests for ui_home, ui_intro, ui_level2, ui_level3, ui_level4, and ui_level5 packages.
- Added metadata validation tests for ui_intro, ui_level2, ui_level3, ui_level4, and ui_level5 packages with comprehensive checks for structure and dependencies.
- Created new component cases JSON files for ui_home, ui_intro, ui_level2, ui_level3, ui_level4, and ui_level5 packages to define expected component structures.
- Updated metadata cases JSON files for ui_intro, ui_level2, ui_level3, ui_level4, and ui_level5 packages to include validation patterns and required fields.
- Added a new UI Pages Bundle package with validation tests and comprehensive dependency checks.
- Implemented notification center initialization and rendering utilities.
- Added toast notification types: success, error, warning, and info.
- Created notification list rendering with badge support.
- Included SVG icons for notification center.
- Added tests for notification center functionalities.
feat: introduce schema editor package for database management
- Developed schema editor initialization and field type definitions.
- Implemented table management and relationships handling.
- Added SVG icons for schema editor.
- Included tests for schema editor functionalities.
feat: create user manager package for user management operations
- Implemented user management actions: create, update, delete, change level, and toggle active.
- Developed user list rendering with sortable columns.
- Added SVG icons for user manager.
- Included tests for user manager functionalities.
feat: add workflow editor package for workflow management
- Developed workflow editor rendering and step management utilities.
- Implemented workflow run status display and progress rendering.
- Added SVG icons for workflow editor.
- Included tests for workflow editor functionalities.
chore: add static SVG icons for various packages
