If Facebook returns [], gem should return []. Fixes #350 #351
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
kenips
changed the title
|
Alternatively we should "patch" Facebook's response and return |
|
|
|
👍 thanks!! Sorry wasn't able to respond earlier. I agree with you that this is a Facebook bug and we actually opened a bug report with them too. However they insisted |
|
Hey @nov can we push up v2.7.12 to rubygems.org? Thanks!! |
|
ah, sorry. |
|
No worries. Thanks again!!! |
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.
See #350 - Facebook returns "[]" for some responses. Gem should accept them happily in this case?