export badge configs#241
Merged
Merged
Conversation
pqoqubbw
approved these changes
May 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.
Summary
Update badge configs
Test Plan
Note
Low Risk
Presentation-layer export and typing refactor only; no behavior change to Badge rendering.
Overview
Badge option unions are now driven by shared
as constlists (BADGE_COLORS,BADGE_SHAPES,BADGE_SIZES,BADGE_VARIANTS) instead of inline string unions, so runtime values and TypeScript types stay aligned.The package public API grows: those constants plus
colorVariantsandsizeVariantsare re-exported frombadgeand the barrelindex, andBadgeVariantis included in the type exports.Reviewed by Cursor Bugbot for commit 3a9a7c5. Bugbot is set up for automated code reviews on this repo. Configure here.