Update Facebook Graph API to v8 #11160
Merged
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
|
@StorytellerCZ the tests seem to be stuck. Sometimes this happen with CircleCI and I don't know why yet. Maybe you could create another PR? |
|
@filipenevola I'll see what I can do to push things. |
|
@filipenevola Fixed! |
filipenevola
approved these changes
Oct 5, 2020
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.
Facebook GraphAPI keeps on quickly evolving. Thankfully there are no changes (that I have noticed) for the OAuth API except for increasing the version number. Still, better be on the newest version just in case Facebook decides to close the older APIs sooner than advertised as a response to some new controversy. Also new Facebook Apps are setup only with the latest v8 API.
Changelog:
https://developers.facebook.com/docs/graph-api/changelog