Fix validation of variable lengths string datasets in Zarr #1348
+63
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Fix hdmf-dev/hdmf-zarr#221.
Zarr does not natively support variable length strings, and validation of vlen string arrays uses the HDF5 specific
data.dtype.metadatafield. This field is None for Zarr arrays resulting in the data type not being correctly extracted during validation using theget_typemethod.How to test the behavior?
Validate an NWB zarr file with an io object input
Checklist
CHANGELOG.mdwith your changes?