-
Notifications
You must be signed in to change notification settings - Fork 11
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
Ticket/18934 #10
Ticket/18934 #10
Conversation
This decouples videos from suites, which makes sense. It also allows for more subtle distinctions of handling vs. not handling video urls.
Also includes some corrections to the core API caught during testing.
Plays nicer with PathMixins, which seem to be a nice way of getting path parsing to multiple loaders. Set up the mixin to layer the endpoint formatting on top of the normal formatting, since it makes things work more "as expected".
Looks like Travis did run the build, and it failed: http://travis-ci.org/#!/pculture/vidscraper/builds/1086383 I haven't looked at the code yet, but it's in my queue. Update: the tests are passing locally for me; not sure what's up with Travis. |
return {} | ||
|
||
|
||
class OEmbedMixin(object): |
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.
It seems strange that this is a mixin, rather than a subclass of VideoLoader
. Is this functionality useful other than when mixed with VideoLoader
?
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.
Actually, it originally was a subclass of VideoLoader; I switched it to a mixin to make it easier to combine with other mixins (specifically, the path mixins used by a couple of suites.)
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.
Yeah, I noticed that you made a commit about that. It's not obvious from the code, however; can you add a comment, or a docstring, about why it's implemented this way?
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.
I've added a note.
Updated update: tests are failing, looks like a Vimeo problem:
|
Travis did run the branch, but it hasn't run the branch since 7cd225f (the first commit in this branch) which is why it failed. The vimeo test does fail, but sporadically - and I'm pretty sure it does the same on the develop branch. |
I think all of the current notes have been addressed; let me know if there's anything else you'd like to see. |
The changes look good. |
This pull request resolves the following tickets:
The actual work involved is a refactor of SuiteMethods into VideoLoaders; it further decouples video data loading from suites.
Travis doesn't seem to be building vidscraper atm, but all tests are passing locally.