-
Couldn't load subscription status.
- Fork 1.1k
Implement VideoPress metadata fetching #20237
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
0b76f70
Update WordPressKit ref to branch
fluiddot e3f7878
Add `getMetadataFromVideoPressID` to `MediaService`
fluiddot 92b43e7
Replace `fetchRemoteVideoURL` with `fetchVideoPressMetadata`
fluiddot 3b1a671
Remove `getMediaURLFromVideoPressID` in favor of `getMetadataFromVide…
fluiddot 2a1f1b8
Pass `isSitePrivate` for fetching VideoPress metadata
fluiddot 14224a4
Update metadata conversion to dictionary
fluiddot 9d78e1b
Update calls to `getPlayURL` with `getURLWithToken`
fluiddot 5fd2d46
Update Podfile.lock with last version of WordPressKit
fluiddot a4da397
Add fetch remote video URL helper
fluiddot 2ca032d
Use `fetchRemoteVideoURL` in Story and Post coordinator
fluiddot e5c0d2f
Update Gutenberg media observer to handle non-VideoPress videos
fluiddot 2a0533a
Update Podfile.lock with last version of WordPressKit
fluiddot 5dce1f5
Handle no token case when using `getURLWithToken`
fluiddot e8204d6
Point `WordPressAuthenticator` to branch
fluiddot e8d43dc
Call completion handler if `originalURL` is not defined after fetchin…
fluiddot cb45330
Use generic error on failure result
fluiddot fc6ff81
Update `WordPressKit` and `WordPressAuthenticator` pods to beta version
fluiddot 12b62ab
Merge branch 'trunk' into add/videopress-metadata
fluiddot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before merging the PR, probably we should check if there are any important changes between
5.1to5.6inWordPressAuthenticator.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point.
The more interesting file to look at is
Podfile.lockwhere WordPressAuthenticator results resolved as version 5.5.0.The only differences between 5.5.0 and 5.6.0-beta.1 are of course all and only the changes bundled with 5.6.0-beta.1, and those are nothing more that the WordPressKit major version bump, which this PR verified.
I think this version requirement change is safe to merge. Even if an issue was introduced in going from
~> 5.1-betato~> 5.6-betathe culprit would not be in 5.6.0-beta.1There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, was there a requirement in the code for something that came in WordPressAuthenticator 5.6.0?
Otherwise, we could have left the requirement as it was and trust in CocoaPods to resolve the correct WordPressAuthenticator version compatible with WordPressKit 7.0.0-beta.1.
Out of curiosity, I reverted this change on my machine and everything worked fine.
No big deal, though. We'll soon need to actually updated WordPressAuthenticator anyway: #20128
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good point. I thought might be more changes but based on
Podfile.lockthe only one was introduced in 5.6.0-beta.1 🤦 .Actually, there's no change required in this PR from
WordPressAuthenticator. However, when I upgradedWordPressKitto version 7.0 (reference), I was getting an error when installing theWordPressAuthenticatorpod related to the minimum version. Due to this, I had to create wordpress-mobile/WordPressAuthenticator-iOS#754 and bump the minimum version of WordPressKit dependency to 7.0.However, I've reverted the changes as you mentioned and I'm not getting now the error 🤔.