Anshul Singhvi
Anshul Singhvi
I guess we could wrap Documenter usage in `withenv("GKSwstype" => "100") do ... end`. But yeah, if it's a performance improvement it seems reasonable not to drop it.
I had never tested on a monorepo with multiple documentation builds so I probably missed something in the deployment pipeline. There are a couple of issues here. - The `final_site`...
` clean_md_output = isnothing(settings.clean_md_output) ? deploy_decision.all_ok : settings.clean_md_output` is the way I try to get defaults out, so clearly `deploy_decision.all_ok` is false. This is borne out by ``` ┌ Info:...
I think you can pass a deploy config in a kwarg to both MarkdownVitepress and deploy docs for now, but I'll patch the constructor so you can pass deploydocs kwargs...
I would suggest you add an error hinter via `Base.Experimental.register_error_hint` that triggers on MethodErrors - if the function is `fooplot`, you can then check if the extension is loaded or...
How would this fit in with an auto-legending or auto-colorbar request?
Would be nice to have more info on what you want to integrate (and for what usecase). Is it just polygons from h3 as some form of struct, or do...
Expand on hover would be good, and they should also be clickable as is.
Yeah only when tagging! But maybe we can build this into deploydocs
Oops - will look into that at some point. An MWE is probably not too hard to create on the MarkdownAST end from the tree you posted.