Payload Versioning #12
Open
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
| def find_conditions(id) | ||
| id.kind_of?(Hash) ? cleanse_id(id) : {multiple_man_identifier: id} | ||
| def find_model(payload) | ||
| model_class.where(cleanse_id(payload.identify_by)).first || model_class.new |
There was a problem hiding this comment.
can use .first_or_initialize here
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.
Allow payloads to be versioned in MultipleMan. This helps us move message formats forward and make a "clean break" from the past by isolating differences in message payloads to a particular version.
Right now there's only one version to process, so this doesn't do much, but I wanted to have an "official" multiple man version to introduce the versioning on (Payload V2 will come in MM 1.1)