4 ms·
Leaflet is great, but I would steer clear of any library that attempts to wrap it to work with a different API (aka Angular-Leaflet). Several weeks of my life
by alexbanks 10y ago
Leaflet is great, but I would steer clear of any library that attempts to wrap it to work with a different API (aka Angular-Leaflet). Several weeks of my life were spent trying to get our Angular app to play nice with Angular-Leaflet, and we ultimately decided Angular-Leaflet was too much of a mess to keep around.
- knz 10y agoI'm curious what approach you used after giving up on angular-leaflet? I've had a similar experience moving apps to Angular and working with Angular leaflet. Thankfully I work with a great consultant so didn't lose weeks but angular-leaflet is definitely not the clean experience that leaflet.js is.
- alexbanks 10y agoI ended up writing an Angular directive that modified the DOM via jQuery. It was gross, but it took Angular out of the equation and allowed the implementers of the directive to still use Angular and still have the same functionality they wanted.
- CalRobert 10y agoHmm.. I have a small project I'm working on using Angular Material and Leaflet. I had to make one small change to Angular (annoying since I can't use a CDN) but aside from that I'm happy. If you're curious, you can see an early example at https://www.lanesurfing.com/ https://www.lanesurfing.com/
- jbhatab 10y agoagreed. just use it raw. Or with mapbox
- mcjiggerlog 10y agoWent through the same pain making http://mountains.io http://mountains.io a few years back! Definitely use the native library.