-
Notifications
You must be signed in to change notification settings - Fork 20
Extend mapping of variables in the ui_config to ui elements in the app #1641
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
willyogo
wants to merge
9
commits into
canary
Choose a base branch
from
codex/extend-ui-element-mappings-with-ui_config
base: canary
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.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
0234807
Align UI elements with community font settings
willyogo ebe36e6
Apply ui-config background color across UI surfaces (#1642)
willyogo 92b8fe7
Align tab and customize button colors with UI config (#1645)
willyogo 91ef881
Adjust nav border styling (#1647)
willyogo cd3aa53
Adjust nav border thickness (#1648)
willyogo 2695ddd
Fix UI hook ordering and simplify Customize button states (#1649)
willyogo 425267c
Align notifications page with ui_config styling (#1650)
willyogo c102160
Adjust cast modal borders for background blending (#1651)
willyogo 43cb095
Apply ui config styling to cancel cast prompt (#1652)
willyogo 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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Hardcoded colors break theming consistency; secondary text color lacks visual hierarchy.
Two issues here:
Lines 337-338:
tabBarBackgroundandborderColorare hardcoded asrgba(128, 128, 128, 0.2), which bypasses the theming system. These should be derived fromuiColors(e.g., semi-transparent variants ofbackgroundColoror provided by the hook).Line 339: Setting
secondaryTextColor = uiColors.fontColordefeats the purpose of having a secondary text color. Secondary text typically requires reduced opacity or a lighter shade to establish visual hierarchy.🔎 Suggested approach
Consider deriving these values from the theming system:
const uiColors = useUIColors(); const castButtonColors = useMemo( () => ({ backgroundColor: uiColors.castButton.backgroundColor, fontColor: uiColors.castButtonFontColor, }), [uiColors.castButton.backgroundColor, uiColors.castButtonFontColor] ); - const tabBarBackground = "rgba(128, 128, 128, 0.2)"; - const borderColor = "rgba(128, 128, 128, 0.2)"; - const secondaryTextColor = uiColors.fontColor; + // Derive from theme or add to useUIColors hook + const tabBarBackground = `${uiColors.backgroundColor}cc`; // or from hook + const borderColor = `${uiColors.fontColor}33`; // 20% opacity + const secondaryTextColor = `${uiColors.fontColor}cc`; // 80% opacityAlternatively, extend the
useUIColorshook to return these derived values for consistency across components.📝 Committable suggestion
🤖 Prompt for AI Agents
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.
while it's true that the tabBarBackground and borderColor are hardcoded, they are semi-transparent, meaning they will always match the background. in the future we may add some vars to ui_config for these greys, but for now hardcoding is sufficient
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.
@willyogo, that makes sense—semi-transparent greys will indeed blend with the background regardless of the theme. I appreciate the context that ui_config vars for these values may be added later. The current approach is reasonable for now. 👍