Scope
Update the architecture and build so that we build the schemas in the repo. This will allow us to extended them to add constraints and additional checks in future work. The schema repo should now pull in all the packages similar to how docs does for org to extra each repos schema. A single package should be built and released by the schema repo, this will allow consumers such as the PatternFly MCP to use the PatternFly component schemas.
Approach
- Agree the package priority list (start with react-table to close the known Table schema gap).
- Add matching
propsGlobs include/exclude entries (mirror react-core excludes: examples, tests, mocks) to each repo.
- Run
build:props / generate-props, confirm new component keys in props.json and schemas for each repo.
- Generate and publish patternfly-component-schemas; bump consumers (e.g. patternfly-mcp) and verify schemas for newly covered components (e.g. Table
isSchemasAvailable: true).
Jira Issue: PF-4533
Scope
Update the architecture and build so that we build the schemas in the repo. This will allow us to extended them to add constraints and additional checks in future work. The schema repo should now pull in all the packages similar to how docs does for org to extra each repos schema. A single package should be built and released by the schema repo, this will allow consumers such as the PatternFly MCP to use the PatternFly component schemas.
Approach
propsGlobsinclude/excludeentries (mirror react-core excludes: examples, tests, mocks) to each repo.build:props/generate-props, confirm new component keys inprops.jsonand schemas for each repo.isSchemasAvailable: true).Jira Issue: PF-4533