Anshul Singhvi
Anshul Singhvi
https://github.com/JuliaIO/Zarr.jl/blob/1275f422c1b71ca2960f8c172321a66a17ed313e/src/Compressors/Compressors.jl#L55 exists so I am very confused
`getgeom` doesn't work for Features by definition though, we may want to change the API spec in some theoretical 2.0 to make that work? I guess the idea back then...
yeap ``` julia> ax.elements[:yminorgridlines].args[1][] 79999990-element Vector{Point{2, Float32}}: [44.0, 39.00001] [584.0, 39.00001] [44.0, 39.00003] [584.0, 39.00003] [44.0, 39.00004] [584.0, 39.00004] [44.0, 39.00005] [584.0, 39.00005] [44.0, 39.00006] [584.0, 39.00006] ⋮ [44.0, 433.99997]...
It would be great to have these as "keyword arguments" to the example/repl blocks as well - as well as maybe some defaults on the page level, settable via `@meta`....
We can use that as a comparison between commits ala Makie. But true comparison means running all benchmarks from all languages on the same machine which isn't realistic on CI.
Let's get this in!
@tiemvanderdeure I think you have to approve the PR for merging to work
Let's do this after v3 lands? Otherwise it will be a mess
A mention in the docstring about the source of the heuristic would be nice, but we (maintainers) have to update the reference images
I think what Rafael is asking for is, given a specific ZArray, can you get the path to that array within the dataset?