Fix Form Loose Dirty Fields Values After Cancelling Navigation #6005
Conversation
This file contains 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
fzaninotto
requested changes
Mar 7, 2021
| @@ -1,17 +1,18 @@ | |||
| import * as React from 'react'; | |||
| import { FC, useRef, useCallback, useEffect, useMemo } from 'react'; | |||
djhi
force-pushed
the
fix-warn-when-unsaved-changes
branch
from
53c6208 to
569bf17
Compare
|
Needs rebase again |
djhi
force-pushed
the
fix-warn-when-unsaved-changes
branch
from
569bf17 to
7ba378c
Compare
fzaninotto
approved these changes
Mar 8, 2021
This was referenced Mar 13, 2021
|
This change likely caused a regression in the handling of default values in Edit forms (see #6198) |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Fixes #5081
Tried locally with the same setup as in the issue