-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
Not compatible with react-leaflet v3? #123
Comments
Hey hi, @barbalex Thank you for creating the issue. Don't know, how long the migration to v3 could take, as that is just my pet project. Would read the v3 documentation during those weekends, and will try to migrate it (= |
Things are changing 🙃 |
I think I have a solution - do you want a PR? |
That would be awesome, as I'm stuck a bit at work. |
Any update on this? |
Needs some more testing, but works as well as the previous solution |
@CodeCutterUK Many thanks for your contribution! Your PR #124 has been merged and improved at #125 === yarn add react-leaflet-markercluster@next # yarn
npm install react-leaflet-markercluster@next # npm Hope that will find some time to improve it. After some testing period will update and republish it as a release package. Thank you very much 🍻 🍻 🍻 |
I tested version 3.0.0-rc1 in my app and it seems to work well. Thanks @CodeCutterUK and @yuzhva ! |
@yuzhva Looks like Or I may be missing something. (Using |
@agorf ✅ Just updated them. |
I tried upgrading my project to react-leaflet v3.0.0.
This is the component I tested: https://github.com/barbalex/apf2/blob/3c90de3a89c23ac720ccae00dc9bdedb71cfd6d0/src/components/Projekte/Karte/layers/Pop/index.js#L166-L175
It works well with react-leaflet v2.8.0 and react-leaflet-markercluster v2.0.0.
It breaks when using react-leaflet v3.0.0, causing this error:
I guess this is not surprising as react-leaflet v3 is a complete rewrite. For instance, accessing the map has changed.
The text was updated successfully, but these errors were encountered: