Fix Dirty API to compare objects of custom type using dumps #851
Conversation
This file contains 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
Add field's option :comparable that affects how old and new objects of custom type are compared - by comparing dumps or using #== method.
andrykonchin
force-pushed
the
ak/don-require-custom-type-to-implement-equality-method
branch
from
f7cca53 to
9604f25
Compare
Minimum allowed line rate is |
andrykonchin
deleted the
ak/don-require-custom-type-to-implement-equality-method
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.
Changes:
#==method:comparabledynamoid_dump/dynamoid_loadmethods) toMarshal.dump/Marshal.loadThe option
:comparableaffects how old and new objects of custom type are compared - by comparing their dumps or using#==method. If it is true - objects are compared with#==. They are compared by comparing dumps otherwise.Example:
Close #848