feat: split ExoMetadataProps into base and Experience-extended variants [DX-987]#3008
Merged
Tyler Pina (tylerpina) merged 2 commits intofeat/exofrom Apr 28, 2026
Merged
Conversation
…X-987] ExoMetadataProps no longer includes name — aligns with upstream MetadataSchema used by ComponentType and Template. New ExperienceMetadataProps extends the base with name? for variant labeling, mirroring upstream ExperienceMetadata. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Bito Automatic Review Skipped - Branch Excluded |
Michael Pham (michaelphamcf)
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DX-987
Summary
ExoMetadataPropsinto two types: base (tags + concepts, used by ComponentType and Template) andExperienceMetadataPropswhich extends the base withname?(used only by Experience)experiences-api-schemaswhich defines a baseMetadataSchemaand a separateExperienceMetadatathat addsnameExperienceCommonProps.metadatanow usesExperienceMetadataProps; ComponentType and Template are unchangedTest plan
npx tsc --noEmitpasses with no errorsnpm run test:unitExoMetadataPropsno longer hasnamefieldExperienceMetadataPropsextendsExoMetadataPropsand addsname?{ name: 'foo' }toExoMetadataPropsproduces a type errorGenerated with Claude Code