Add classes for generic usages of (status) field borders#204
Merged
chanagaray merged 1 commit intojdan:mainfrom Nov 30, 2024
Merged
Add classes for generic usages of (status) field borders#204chanagaray merged 1 commit intojdan:mainfrom
chanagaray merged 1 commit intojdan:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
frankier
force-pushed
the
add-field-borders
branch
from
e018ccd to
4674ef9
Compare
Collaborator
|
Thank you! |
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.
I opted to add classes for these. The reason is is that the remaining reasons are somewhat generic and don't have a clear scope in terms of semantic tags. I believe the quoted text from the Microsoft Windows User Experience supports this.
Fixes #73