-
Notifications
You must be signed in to change notification settings - Fork 402
refactor(clerk-js): Make color ring and modal-backdrop full opacity when modified #7052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
alexcarpenter
wants to merge
2
commits into
main
Choose a base branch
from
alexcarpenter/variables-ring-color
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+10
−10
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
LGTM! Verify the breaking change impact across the codebase.
The removal of the forced
0.85transparency wrapper correctly implements the PR objective, allowing users to specify exact colors and opacities. The pattern now matches other optional color properties likecolorMutedandcolorShadow.However, this is a breaking behavioral change. Existing code or user configurations that rely on the automatic transparency will now see
colorRingat full opacity unless they explicitly specify a transparent value.Run the following script to identify any usages that might be affected by this breaking change:
🏁 Script executed:
Length of output: 448
🏁 Script executed:
Length of output: 13165
🏁 Script executed:
Length of output: 528
🏁 Script executed:
Length of output: 1598
Update JSDoc to reflect breaking change in colorRing opacity behavior.
The removal of
makeTransparent(0.85)wrapper is a breaking change for users providing explicitcolorRingvalues. The JSDoc atpackages/types/src/appearance.ts:757-759currently states the color is rendered "at 15% opacity," but this guarantee no longer applies when users provide a custom value—they now get full opacity unless explicitly specified.Update the documentation to clarify:
colorRingis undefined, the default uses 15% opacitycolorRingis explicitly provided, users control the opacity (no forced transparency)The implementation itself is correct and matches the pattern of adjacent optional color properties (
colorMuted,colorShadow). The consuming code acrossbaseTheme.ts,styledSystem/common.ts, and UI components will work correctly with this change.🤖 Prompt for AI Agents