-
Notifications
You must be signed in to change notification settings - Fork 76
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
Migration Feedback #305
Comments
@aavmurphy Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
Thanks for capturing these. There are definitely some tradeoffs that were made and I think this library was an early attempt to provide the flexibility that was lacking in previous versions. One of the questions going forward will be additional forms of rendering. The previous marker clustering implementation used Another question is the input data. It's difficult to support all of the edge cases around visibility, setMap, etc as captured in #267. Should we allow something like geojson? As to speed, markers are definitely the bottleneck on both ends however there is ongoing work that may improve this on the rendering side. Already available at unpkg.
Anyone can submit a pr to have support in CDNJS. https://github.com/cdnjs/packages |
An update, checking if I can upgrade to the current (2.5.3) version from legacy clusterer https://github.com/mahnunchik/markerclustererplus The points I made above are still valid
(Note : I was using Advanced Markers when testing, the legacy clusterer doesn't support them) |
[Sorry for multiple points in the same issue]
Migrating from (depreciated) https://github.com/mahnunchik/markerclustererplus to v2.0.4
Hope this helps.
The text was updated successfully, but these errors were encountered: