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

Setting a non-field shouldn't save to the db. #16

Merged
merged 3 commits into from
Apr 26, 2016

Conversation

pcraciunoiu
Copy link
Contributor

No description provided.

Jay O'Conor added 2 commits April 26, 2016 11:16
…n attribute defined in the class. This is usually the case with a property, but could conceivably happen with any attribute name that mirrors a class attribute.
@joconor
Copy link
Contributor

joconor commented Apr 26, 2016

👍 Paul: I made a couple changes that illustrate the problem I was seeing, as well as fixes the problem. Please review the test & the fix. My analysis of the uses of _key_value_to_dynamodb() looks like this should be a clean fix, but you should verify this as well.

@pcraciunoiu
Copy link
Contributor Author

👍

@joconor joconor merged commit 0b7b918 into master Apr 26, 2016
@joconor joconor deleted the feature/test-non-field branch April 26, 2016 19:46
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.

2 participants