This repository was archived by the owner on Aug 16, 2019. It is now read-only.
Deletion populator and multiple new records #128
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
I found out that using the default example for deletion Populator does not allow to have multiple new items added to collection. In this case all new fragments do not have `id`. So find matcher will return the wrong item since `song.id.to_s == fragment["id"].to_s` (nil == nil) will always be true from 2nd run. I suggest we additonally check for id presence.
alex-lairan
reviewed
Apr 16, 2018
| populator: ->(fragment:, **) { | ||
| # find out if incoming song is already added. | ||
| item = songs.find { |song| song.id.to_s == fragment["id"].to_s } | ||
| item = songs.find { |song| song.id.present? && song.id.to_s == fragment["id"].to_s } |
There was a problem hiding this comment.
The #present? method not exist.
1.present?
NoMethodError: undefined method `present?' for 1:Fixnum
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I found out that using the default example for deletion Populator does not allow to have multiple new items added to collection.
In this case all new fragments do not have
id. So find matcher will return the wrong item sincesong.id.to_s == fragment["id"].to_s(nil == nil) will always be true from 2nd run.I suggest we additonally check for id presence.