Skip to content

Commit

Permalink
import Zarr.typestr when necessary
Browse files Browse the repository at this point in the history
  • Loading branch information
@asinghvi17
asinghvi17 authored Sep 14, 2024
1 parent f57bea1 commit 1a2ddf9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/required_zarr_filters.jl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ we can register Kerchunk and users can use it without Zarr being an issue.
=#

import Zarr: Filter, zencode, zdecode, JSON, getfilter, filterdict
import Zarr: Filter, zencode, zdecode, JSON, getfilter, filterdict, typestr

#=
# Delta compression
Expand Down

2 comments on commit 1a2ddf9

@asinghvi17
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request updated: JuliaRegistries/General/114971

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.0 -m "<description of version>" 1a2ddf9116198c3a419ba2e3c7800a9c0c565438
git push origin v0.1.0

Please sign in to comment.