style: replace hardcoded color #9ab3c0 with dusty-blue variable#8041
Merged
alexander-akait merged 1 commit intowebpack:mainfrom Mar 17, 2026
Merged
style: replace hardcoded color #9ab3c0 with dusty-blue variable#8041alexander-akait merged 1 commit intowebpack:mainfrom
alexander-akait merged 1 commit intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexander-akait
approved these changes
Mar 17, 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
This PR replaces several instances of the hardcoded hex color #9ab3c0 with the existing $colors map variable dusty-blue using the getColor() function. This improves theme maintainability and ensures consistency across the codebase.
What kind of change does this PR introduce?
Refactor (code quality improvement and consistency enhancement).
Did you add tests for your changes?
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
No additional documentation is required. The change follows the existing theming conventions already documented in the project.
Use of AI
No