Enhance Visual Differentiation for Similar Regex Components #153
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
|
@ymzkei5 is attempting to deploy a commit to the Bowen's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bowen7
approved these changes
Apr 11, 2025
Owner
|
Looks good to me |
Contributor
Author
|
Thank you! |
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.
Currently, the app uses the same line style and color for pairs of elements such as "one of" vs. "none of", "Preceded by:" vs. "Not preceded by:", and "Followed by:" vs. "Not followed by:". This similarity can make it hard to quickly distinguish between components that have different logical meanings.
Therefore, I wanted to change these line styles and colors. The goal of this PR is to enhance the clarity and visual communication of regex components. By differentiating these elements visually, users can more easily parse and understand complex regular expressions.
However, I fully understand and respect that the current design may have been chosen for specific reasons. My intention is simply to propose a possible enhancement, not to override any existing design decisions.