Fix for issue 8631: field values are reset when imported#8632
Merged
MatteoPiovanelli merged 2 commits intoOct 14, 2022
Conversation
…PickerField, the field doesn't need to be reset.
…resetting the field value even if the field isn't imported. This applies to ContentPickerField, MediaLibraryPickerField and NumericField.
|
|
sebastienros
approved these changes
Oct 13, 2022
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
4 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.
This fixes #8631 , adding a check on the existence of the importing element inside the context. If the field isn't inside the context, the field is not imported (previously its value was being reset).