I'm trying to get my head around how the read function is specified. It seems like datastorr::github_release_info() wants to get the name of a currently available function before it will run successfully. datastorr.json can also serve as a place to store that information.
Should datastorr::github_release_info have a default argument, where the read function is just allowed to be whatever is specified in the datastorr.json file?
On the other hand, it seems dangerous for a function's behaviour to be modified by a change to a file on github! (i.e. if datastorr.json changes, then the output of datastorr::github_release_info changes too.). Perhaps it should supply a warning if the datastorr.json function is used?
Similarly, should datastorr::github_release_info check for the existence of a datastorr.json file?
I'm trying to get my head around how the
read
function is specified. It seems likedatastorr::github_release_info()
wants to get the name of a currently available function before it will run successfully.datastorr.json
can also serve as a place to store that information.Should
datastorr::github_release_info
have a default argument, where theread
function is just allowed to be whatever is specified in thedatastorr.json
file?On the other hand, it seems dangerous for a function's behaviour to be modified by a change to a file on github! (i.e. if
datastorr.json
changes, then the output ofdatastorr::github_release_info
changes too.). Perhaps it should supply a warning if thedatastorr.json
function is used?Similarly, should
datastorr::github_release_info
check for the existence of adatastorr.json
file?