Repository navigation
Update patternfly packages to pull in the component schemas from doc core #236
Description
Activity
🔗 Related PRs
#221 - feat(API): [PF-3167] Add component-index.json API endpoint for MCP [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
- changed the title
[-]add other pf-react pkgs to config propsGlob for inclusion in component schemas[/-][+]Update patternfly packages to pull in the component schemas from doc core[/+]on Aug 13, 2026
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
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