Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reduced permission for Google Drive
See original GitHub issueI was very happy to install this and find Google Drive support - makes using it much lower friction for me.
However it currently requiers full access to Google Drive. This doesn’t feel right - the extension should only have access to my vault archive(s), not all my personal documents.
The appropriate scope for this is https://www.googleapis.com/auth/drive.file
If buttercup creates the archive I think this is straightforward. But if a user wants to use an existing archive it will require some rework for the flow - I’m not sure how a user gives access to a specific file.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Seems this works out of the box. Existing vaults that have been accessed remain accessible to Buttercup:
(This was after reducing the permissions scopes)
This will come out soon. Might even help fix #314.
Oh yes, importing seems like a great alternative to uploading.