Peg VimeoMe2 at version 3.2 of the Vimeo API #10
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
|
Any idea how long 3.2 will be supported by Vimeo? |
|
They should be supporting it for a while (several months at least since 3.0 is still available), but not sure. |
bo-oz
approved these changes
Apr 1, 2018
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.
Vimeo API version 3.4 contains some breaking changes to things such as upload (for example syntax for upload is now post body including:
{'upload': { 'approach': 'method' }}). The endpoints implemented by VimeoMe2 all seem to work up to at least version 3.2.See https://developer.vimeo.com/api/changelog#34 for more details