Prevent recording uppercase status in update database - #3405
Merged
Conversation
don't change updateAttr status after save into update page
zoic21
approved these changes
Jun 30, 2026
Salvialf
approved these changes
Jun 30, 2026
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
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.
Don't change updateAttr status after save into update page
Description
Currently, when clicking "Check for updates" the status is saved in lowercase. in display, the JavaScript forces the attribute to uppercase and if the user saves, the attribute is now saved in uppercase
click

Check for updates:click

Save:The modification I am proposing consists of displaying the status in uppercase using only CSS, thereby leaving the status in its raw format.
Suggested changelog entry
Related issues/external references
Fixes #
Types of changes
PR checklist