-
Notifications
You must be signed in to change notification settings - Fork 436
205 - Pager/Fetcher all the things! #231
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
205 - Pager/Fetcher all the things! #231
Conversation
@@ -70,15 +70,24 @@ def add(self, user_item): | |||
# Get workbooks for user | |||
@api(version="2.0") | |||
def populate_workbooks(self, user_item, req_options=None): | |||
from .. import Pager |
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.
Why do this here?
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 did that on the 'users-in-groups' bugfix and just copied the pattern.
Don't think there's a great reason, just how I did it before.
I can move it to a top-level import
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.
🚀
Here's a
checkpointPR for where I'm at in concerting all the models to 'fetch-on-demand' after you callpopulate_XXX
on something.Mostly it's a straight forward conversation but a few places have some interesting caveats so posting here for feedback.
EDIT: I've converted all the endpoints, I believe, so they all have on-demand fetching. WOO.
Also added test coverage where there wasn't any. This covers @grbritz's bug as well