Skip to content
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.

Sign up for GitHub

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

Jump to bottom

be strict about input to to_zarr #22

Open
d-v-b opened this issue Dec 13, 2023 · 0 comments
Open

be strict about input to to_zarr #22

d-v-b opened this issue Dec 13, 2023 · 0 comments

Comments

@d-v-b
Copy link
Collaborator

d-v-b commented Dec 13, 2023

Currently, to_zarr can take a zarr.Group as input and errors will only appear from deep in the zarr codebase, errors which fail to convey the source of the problem (i.e., providing the wrong type as input). We should add a type guard to check for this and produce a useful error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@d-v-b