-
Notifications
You must be signed in to change notification settings - Fork 62
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
Add Google Drive board #749
Conversation
We should definitely not run the tests for |
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.
Any hope of speeding it up by caching drive ids somewhere?
I don't believe so. There's no "extra" mapping between drive ID and something else that we can cache somewhere (like the Connect mappings from GUID to content name). Just for clarity here, the normal pins caching mechanism does work as expected here, so you don't re-download pin content if it hasn't changed. However, even the process of looking up the pin metadata to check this feels sluggish. |
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Closes #728
Wow, using Google Drive for this is not speedy 😳