-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Leaflet 1.0.1 #169
Conversation
Leaflet draw might have to be updated as well no? (0.4 for 1.0 comptability) |
Proj4Leaflet is not 1.0 compatible yet:
|
Probably worth waiting for things to be resolved over there before creating a new release here. |
Proj4Leaflet 1.0.0 is out. |
Can someone please try out and approve the changes of this branch? |
You know what. I'll merge, 'cause I'm feeling lucky :) |
I have not tested it carefully yet, so it'd be worth if someone would try it out. |
I released version 0.20 with the upgrade. Issues will be opened if there are bugs... «Release early» they say :) |
i'm getting a bunch of bugs with leafletforms.js and leaflet.draw.js regarding mulitpolygons that i didn;t have with version 0.7 (eg these templates used to work.....): original error regarding multipolygon: i hacked that with |
I'm not surprised that bugs were introduced. Don't hesitate to open a pull-request with some fixes, we'll release. We're looking for maintainers! ...currently overlooking patches, merging and releasing is the only thing I can do, at a very low frequency |
it has something to do with the widget (obviously). there seems to be some incompatibility with the L.GeometryField class and leaflet 1.0. is this a dependency that needs to be updated too? I've dug back to here: that's the line in the widget template, and here's how its rendering:
I haven't dug through too much of the nuts and bolts of django-leaflet since it always worked so well! when I get it fixed i'll make pr |
Issue #166.