Status string capitalization #114
Merged
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
rehsfl
requested review from
Uzichow,
ValentinBoudevin,
moh60 and
mrodriguezg1991
mrodriguezg1991
approved these changes
Oct 21, 2025
Contributor
|
LGTM but squash tests in your commit + add a description |
- Modify VEX assessments labels in frontend to have a consistant naming scheme, as the labels had inconsistant capitalization - Update tests
rehsfl
force-pushed
the
status-string-capitalization
branch
from
9f2aa60 to
fc9b80d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Changes proposed in this pull request:
Status
How to verify this change
Open the web dashboard and notice status naming is consistent across the app, including in graphs and assessments
Pull Request Checklist
Please review and check all that apply before submitting your PR: