-
Notifications
You must be signed in to change notification settings - Fork 4.7k
feat($config): Allow override of badge colors #1472
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
Conversation
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.
Thanks, and could you also help update the docs and create a PR for 1.x?
lib/default-theme/styles/config.styl
Outdated
@@ -4,6 +4,9 @@ $textColor = #2c3e50 | |||
$borderColor = #eaecef | |||
$codeBgColor = #282c34 | |||
$arrowBgColor = #ccc | |||
$badgeGreen = #42b983 |
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.
Could "$badgeTip" be better?
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.
Good call. Updated 👍
Could you also help update the docs and create a PR for 1.x? Related docs: |
Yes, sure thing. Thanks for the refs. |
Any update on this thread? This looks good to me. Could you merge? Thanks! |
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.
@ulivz I've updated the v0 documentation
Hey @bb220, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚 |
Summary
Allow badge colors to be overridden via https://vuepress.vuejs.org/default-theme-config/#simple-css-override
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
n/a
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: