Repository navigation
Color "if"s in conditional imports/exports - #18
Merged
Merged
Conversation
This was referenced Jun 14, 2021
devoncarew
approved these changes
Jun 14, 2021
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.
This adds colour to the
ifs in conditional imports (previously they were white):I've marked them as "control keywords" to match the color of other
ifs in the program, although I'm not sure if that logic is entirely sound. Having them a different color to otherifs looked a little odd (in this theme, control keywords are pink and other keywords blue).(I've done the same in LSP semantic tokens version - we should keep them in-sync if we decide to change it here).
@devoncarew