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
We have been using URI.js for some years now to parse map layer urls.
These contain {s} {x} {y} {z} parameters and are auto-replaced by leaflet or mapbox.
Now, suddenly our code breaks when updating an app because of the change in #344
Is there a way to allow these characters again? Or a least provide us with the option to define the allowed characters on which the url is valid.
Thanks
The text was updated successfully, but these errors were encountered:
I'm currently on vacation so nothing is happening in the next 2 weeks. Please stick to v1.18.10 for now. I'm closing this issue, because it's already tracked in #354. I'm sorry for the inconvenience :(
We have been using URI.js for some years now to parse map layer urls.
These contain {s} {x} {y} {z} parameters and are auto-replaced by leaflet or mapbox.
Now, suddenly our code breaks when updating an app because of the change in #344
Is there a way to allow these characters again? Or a least provide us with the option to define the allowed characters on which the url is valid.
Thanks
The text was updated successfully, but these errors were encountered: