Repository navigation
feat(schema): optional label on selection component options - #260
Open
vydimitrov wants to merge 1 commit into
Open
vydimitrov wants to merge 1 commit into
vydimitrov wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
This branch has not been deployed
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
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.
Adds an optional
label(string | null) to selection component options inSelectionConfigSchema/SelectionConfigInputSchema.The Crystallize API now accepts a label on each selection option. Without this change,
OperationsSchema.safeParsestrips the field, so shapes created through mass operations (imports, CLI) silently lose their labels. The test pins thatlabelsurvives ashape/createoperation.Needs a version bump/publish so the backend can pick it up.
🤖 Generated with Claude Code