We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
NULL
Currently, when an object is created any empty fields are filled with an empty object of the expected class. For example:
db <- connect("laminlabs/cellxgene") artifact <- db$Artifact$get("KBW89Mf7IGcekja2hADu") run <- artifact$storage$run
Here run is an empty Run object. Instead we should set it to NULL which would be cleaner and match Python.
run
Run
The text was updated successfully, but these errors were encountered:
Should have mentioned you get an error if you try to access things in the empty object:
> run$id Error in `private$.api$get_record()` at laminr/R/Record.R:234:9: ! Method Not Allowed
Possibly there is another solution to this but avoiding the empty objects in the first place has other advantages
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Currently, when an object is created any empty fields are filled with an empty object of the expected class. For example:
Here
run
is an emptyRun
object. Instead we should set it toNULL
which would be cleaner and match Python.The text was updated successfully, but these errors were encountered: