Fixed objects being shared across contexts #70
Merged
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
…re-shared-across-context-splits
|
Code Climate has analyzed commit 872cb4f and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 67.6% (0.5% change). View more on Code Climate. |
ARMmaster17
deleted the
6-nested-dictionarylist-objects-in-context-are-shared-across-context-splits
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.
Summary
This PR fixes an issue where if someone put an object inside a
DataContextand then later split the context, the context splitter would only perform a shallow copy, meaning that modifications to the object would be shared across all contexts for that step.The issue is resolved in this PR by performing a deep copy. A regression test has also been added to ensure that this bug does not appear again.
Closes #6