Correct the copy for dict_object#284
Merged
Merged
Conversation
wboereboom
previously approved these changes
Dec 21, 2023
Aleffio
reviewed
Dec 21, 2023
Aleffio
approved these changes
Dec 21, 2023
wboereboom
approved these changes
Dec 21, 2023
Merged
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
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.
Description
To avoid this the
additionalDataremove for the original object create a deep copy (copying nested objects ).This way, the function
is_valid_hmac_notificationwon't affect the originaldict_objectdue to the use ofcopy.deepcopy()creating a independent copy of the objectTested scenarios
add unit test
Fixed issue:
fixes: #278