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.
As discussed in the ZEP call last week, this is a first pass at creating a "global storage transformers" concept, to be applied at the store (rather than array) level.
There are a few things that need cleaning up here:
zarr.json
But before doing that, I thought I would solicit some feedback on this. Does anyone see any fundamental problems with this concept? My motivating use case is #154.
My main open question is: when both array and global storage transformers are defined, what determines the order in which they are applied? The only feasible choices appear to be to apply all the global transformers either before or after the array transformers. Should we make this an option in the protocol?