Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed to Default Value Behavior #71

Merged
merged 4 commits into from
Jun 15, 2017
Merged

Changed to Default Value Behavior #71

merged 4 commits into from
Jun 15, 2017

Conversation

awood45
Copy link
Member

@awood45 awood45 commented Jun 15, 2017

Resolves an issue where the class-level default value could be mutated, and carry across items. Additionally, ensures that mutated default values are not clobbered by eagerly hydrating them at item creation time.

Addresses #69 and a replacement for #70

natesalisbury and others added 3 commits June 13, 2017 16:09
Adds an integration test and unit tests to check for future
regressions. The primary change is that a new `ItemData` object will
hydrate with default values immediately on creation, which triggers the
deep copy presented in earlier commits to this branch.
@coveralls
Copy link

coveralls commented Jun 15, 2017

Coverage Status

Coverage increased (+0.1%) to 98.193% when pulling 5afbf75 on issue69 into 7e4d6a1 on master.

@awood45 awood45 merged commit ac0995a into master Jun 15, 2017
@mullermp mullermp deleted the issue69 branch March 8, 2023 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants