Prepare for Leaflet 2.x #67
Description
There have been several ups and downs while keeping an eye on Leaflet development, but it looks like this integration can be fully compatible without breaking its own API.
Why is Leaflet 2 without polyfill incompatible?
Besides Leaflet core, this module also integrates several 3rd party plugins, and especially leaflet_markercluster seems essential (as a sub-module is built on top of it). Those 3rd party libs aren't compatible and probably never will be (unmaintained...). Forking and maintaining all of them with this project isn't feasible for one person. I'm the only active maintainer here.
This module provides an API for other modules to use the library and extend this module's functionality - this API might break. That's a no-go.
One important sub-module is leaflet_widget, which relies on Leaflet.draw (also an unmaintained 3rd party lib), and is another essential cornerstone of the Leaflet integration in Backdrop CMS. And particularly leaflet_draw broke beyond repair with latest Leaflet commits.
Forking Leaflet.draw isn't feasible, as that's 4700+ lines of code. At least, I'd really want to avoid that.
So: without an option to get markercluster and draw working with 2.x, the move to 2.x simply can not happen.
I'm confident that this is not the only project facing that problem. The current attitude of Leaflet (lib) maintainers re breaking changes (and the amount of breakage) just makes it extremely hard to stay optimistic.
On the other hand, it's their decision...