Anshul Singhvi
Anshul Singhvi
@lazarusA I think you can use `deploy_url` from the MarkdownVitepress object to get the correct / expected URL, and then simply do a string replace on the component if necessary.
Is that one not explicitly named though? Or did a change in the template break it?
ah yeah, problem is that this will break users who have custom config.mts I didn't really think this through when I wrote it :(...maybe we can release a breaking version...
I don't have an example immediately. But imagine a rasterstack with two layers, `u` and `v`. Then `arrows(dimstack, :u, :v)` would just create an arrow plot using `u` and `v`...
Looks like all our convert methods need to invoke convert again on the tuple result.
Also, should `dims2indices` on an extent return a DimUnitRange?
can confirm...even things like axis labels if set explicitly are not respected. mwe: ```julia earth_img = rand(10, 10) earth_ras = DimArray(earth_img |> rotr90, (X(LinRange(-180, 180, size(earth_img, 2)+1)[1:end-1]), Y(LinRange(-90, 90, size(earth_img,...
There is a ci that can check for the oatmeal of a changelog
https://github.com/rafaqz/Rasters.jl/blob/09a29d3936c591fee00e7a14efffa95a4a8d24f1/ext/RastersArchGDALExt/gdal_source.jl#L206-L230 we don't even read the metadata there, is the main issue...
Yeah that would be good, maybe in the constructor then?