Clayton Yochum
Clayton Yochum
All functions except `drop_auth`, `drop_download`, and `drop_upload` now use an internal API wrapper (named like `api_*`) to interact with the Dropbox API. I put all the functions in the relevant...
Many of these API endpoints return one or more metadata objects. We handle them differently in different places, which is not ideal. In `drop_dir`, we flatten the nested output and...
In order to upload a file into a folder without giving it a different (base)name, a user has to build the path themselves, e.g. `drop_upload(file, paste0(folder, "/", file))`. This happens...
We currently have a utility function `add_slashes` that helps deal with the fact the Dropbox API generally expects a starting slash for path arguments, though this isn't always the case;...
We barely use it, so it would be pretty easy to remove. One reason to keep it in would be if we start chaining things together more, esp. if we...
I think `drop_read_csv` defines a really useful pattern: `drop_get` to a local tempfile, then use `read.csv` on it. There's a hard limitation on `read.csv`; if I want to use, say...
The common `oauth_listener needs an interactive environement` (e.g. #64) seems to often be due to `.httr-auth` not being where `drop_auth` expects it to be. This is a pretty unintuitive error...
There's a pattern we keep repeating, particularly for the functions that are super-simple wrappers of the underlying API: ```r drop_foobar
From the binder link, I can't get `PostgreSQL.ipynb` to work as expected; when loading the database, I get `Error: Failed to find shared library for backend postgresql`:  Is it...
Hello, Love this repo! I was trying to modify your example from `#22` to check if _nested_ models are round-tripped unnecessarily if contained within the dict I return in my...