explicit video refs: New API Client #135
Open
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
osdiab
changed the title
osdiab
changed the title
osdiab
force-pushed
the
osdiab/feature/explicit-video-refs-new-client
branch
2 times, most recently
from
b6f35b4 to
d993052
Compare
tinaroh
approved these changes
Nov 2, 2018
osdiab
force-pushed
the
osdiab/feature/explicit-video-refs-shared-models
branch
from
f1e2109 to
782072f
Compare
osdiab
force-pushed
the
osdiab/feature/explicit-video-refs-new-client
branch
from
d993052 to
f3f2cee
Compare
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.
merges into #134, not master
New client sends explicit video references, not tokens