[GSK-1567] Modified button doesnt detect when user goes back to original value #1347
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
henchaves
changed the title
…ct-when-user-goes-back-to
|
Kudos, SonarCloud Quality Gate passed! |
Googleton
approved these changes
Aug 31, 2023
Hartorn
deleted the
feature/gsk-1567-modified-button-doesnt-detect-when-user-goes-back-to
branch
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.
Description
This PR fixes the bug when the user manually change the data inputs back to the original ones, the Inspector keeps displaying a "modified" tag and the selector remains red ("dirty"). Now, if a user changes the input back to the original one, the form remains untouchable.
Related Issue
GSK-1567 (available on Linear)
Type of Change