You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whith Accept: application/vnd.vimeo.video+json;version=3.2 the field is present in the response, with Accept: application/vnd.vimeo.video+json;version=3.4 it is not.
This unfortunately results in a bug with in this library since now the ***SecureLink properties are always null.
As far as I can see, the vales of link and link_secure are always the same with the 3.2 API anyway. So ***SecureLink properties maybe could just be removed. (But I am not an expert on the Vimeo API so maybe there is a difference I am not aware of.)
Since this would be a breaking change, a temporary fix could also be to deprecate the properties, return the values of the regular Links and remove the properties in the next major update.
The text was updated successfully, but these errors were encountered:
Although it is not explicitly mentioned in the changelog (https://developer.vimeo.com/api/changelog#3.4), Vimeo API 3.4 seems to have removed the
link_secure
field.Whith
Accept: application/vnd.vimeo.video+json;version=3.2
the field is present in the response, withAccept: application/vnd.vimeo.video+json;version=3.4
it is not.I don't think it is a bug in the API, because it is also not listed in the current API docs (https://developer.vimeo.com/api/reference/response/video-file).
This unfortunately results in a bug with in this library since now the
***SecureLink
properties are always null.As far as I can see, the vales of
link
andlink_secure
are always the same with the 3.2 API anyway. So***SecureLink
properties maybe could just be removed. (But I am not an expert on the Vimeo API so maybe there is a difference I am not aware of.)Since this would be a breaking change, a temporary fix could also be to deprecate the properties, return the values of the regular Links and remove the properties in the next major update.
The text was updated successfully, but these errors were encountered: