You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, I came into an issue where a slightly misspelled leaflet provider string ended up breaking my whole Quarto document, which was an issue that was tricky to track down!
But what struck me - why can leaflet() chug along happily and render something with an incorrectly specified provider tileset? e.g., if you were to run leaflet(breweries91) |> addProviderTiles("woops") |> addMarkers() you get a broken leaflet map without any markers on it or anything, rather than an error. Could addProviderTiles() not check the provider arg against leaflet::providers to provide a useful error in such cases?
e.g., just an internal check within addProviderTiles() along the lines of:
I'm posting this as it potentially links to quarto-dev/quarto-cli#9897.
In short, I came into an issue where a slightly misspelled leaflet provider string ended up breaking my whole Quarto document, which was an issue that was tricky to track down!
But what struck me - why can
leaflet()
chug along happily and render something with an incorrectly specified provider tileset? e.g., if you were to runleaflet(breweries91) |> addProviderTiles("woops") |> addMarkers()
you get a broken leaflet map without any markers on it or anything, rather than an error. CouldaddProviderTiles()
not check theprovider
arg againstleaflet::providers
to provide a useful error in such cases?e.g., just an internal check within
addProviderTiles()
along the lines of:Created on 2024-06-06 with reprex v2.1.0
The text was updated successfully, but these errors were encountered: