-
Notifications
You must be signed in to change notification settings - Fork 7
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
Support remote repository urls #32
Conversation
For the future, production package the remote URL will be a default argument, and the assay argument will become relevant again. We can imagine the users (90%) query from remote, never touching the |
Agreed
I find this argument a bit weird because it only makes sense if the user is using the default repository. What does it mean if the user uses Could we maybe have |
I see. OK, (I am thinking to a leaner solution) how about for the future, the only arguments available will be main
secondary
If a user institute downloads the local copy of our database, I am thinking in the future, repository argument will never be needed. |
That works, although it will lose the flexibility of having a configurable URL. If we follow my Also, if you want |
I think we need a brief chat at some point.
Let's forget about |
Should I support requesting both assays? ie |
[EDIT] well thinking about this, yes (if it is not incredibly complex). |
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.
Thanks @multimeric ! The only change I would ask is argument names
- cache_dir -> cache_directory (no abbreviation policy, which I also try to use in the back end)
- genes -> feature (singular policy for arguments, and feature respects more the standards)
Well done with the unit tests!
Hmm as a user I find it a bit unintuitive to say |
Oki we can use |
My justification is functions like |
… separate function, add cache to github actions
The CI isn't working, but here is the lint outputs from running it locally:
|
Closes #30.
User-Facing Changes
get_SingleCellExperiment
repository
argument is now the HTTP URL of a remote data source, with a default value pointing to AWS.cache_directory
argument, which points to a local cache.repository
argument, since this was WEHI-specific.data
argument has been renamed todata
according to Tidyverse style: https://design.tidyverse.org/dots-prefix.htmlgenes
argument has been renamed tofeatures
assay
argument has been renamed toassays
get_metadata
repository
andcache_directory
argument that work similarly toget_SingleCellExperiment
Internal Changes
get_SingleCellExperiment
to have tidier codesync_remote_file
,sync_assay_files
, andget_default_cache_dir
, which are utility functions used for this featureTODO
assay
argument, which accepts a string