fix(picker/git_log): provide a dedicated highlight for dimmed conventional commit type #2674
+4
−2
Conversation
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
…ional commit type
noirbizarre
force-pushed
the
fix/git-log-highlight
branch
from
0f30ff4 to
7d1b5ef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
All formatting in the Git pickers use dedicated
SnackPickerGit*highlight groups except the dimmed conventional commit type which is reusingSnacksPickerBold.SnacksPickerBoldis used for Markdown bold formatting and typically themed to be more visible than dimmed which is contradictory with thegit_logusage/intent.This PR simply use a dedicated
SnacksPickerGitTypeDimmedinstead to be consistent.Related Issue(s)
N/A
Screenshots
N/A