-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
feat(ANGULAR GOOGLE MAPS): Is it possible to use the new package @googlemaps/markerclusterer? #23695
Comments
I just asked for that yesterday, they can't change the @types/googlemaps to @types/google.maps for that to work, it's one of the future changes in v13 though. You can use |
I believe #23350 should resolve this. Since the type change constitutes a breaking change, this will be in the next major version (v13). |
Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends. Find more details about Angular's feature request process in our documentation. |
Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage. We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package. You can find more details about the feature request process in our documentation. |
The marker clusterer component is currently based on the `@googlemaps/markerclustererplus` package which is deprecated. These changes rewrite the component to use `@googlemaps/markerclusterer` instead. BREAKING CHANGES: The new clustering package doesn't offer the same set of public APIs. As a result, the following inputs to the `MapMarkerClusterer` component have been removed: * `ariaLabelFn` * `averageCenter` * `batchSizeIE` * `calculator` * `clusterClass` * `enableRetinaIcons` * `gridSize` * `ignoreHidden` * `imageExtension` * `imagePath` * `imageSizes` * `maxZoom` * `minimumClusterSize` * `styles` * `title` * `zIndex` * `zoomOnClick` * `options` The new recommended way of customizing the cluster is to use the `renderer` and `algorithm` inputs. Fixes angular#23695.
The marker clusterer component is currently based on the `@googlemaps/markerclustererplus` package which is deprecated. These changes rewrite the component to use `@googlemaps/markerclusterer` instead. BREAKING CHANGES: The new `@googlemaps/markerclusterer` API should be imported instead of the old one. Read more at: https://github.com/googlemaps/js-markerclusterer Furthermore, the new clustering package doesn't offer the same set of public APIs. As a result, the following inputs to the `MapMarkerClusterer` component have been removed: * `ariaLabelFn` * `averageCenter` * `batchSizeIE` * `calculator` * `clusterClass` * `enableRetinaIcons` * `gridSize` * `ignoreHidden` * `imageExtension` * `imagePath` * `imageSizes` * `maxZoom` * `minimumClusterSize` * `styles` * `title` * `zIndex` * `zoomOnClick` * `options` It is now recommended to customize the cluster using the `renderer` and `algorithm` inputs. Fixes angular#23695.
The marker clusterer component is currently based on the `@googlemaps/markerclustererplus` package which is deprecated. These changes rewrite the component to use `@googlemaps/markerclusterer` instead. BREAKING CHANGE: The new `@googlemaps/markerclusterer` API should be imported instead of the old one. Read more at: https://github.com/googlemaps/js-markerclusterer Furthermore, the new clustering package doesn't offer the same set of public APIs. As a result, the following inputs to the `MapMarkerClusterer` component have been removed: * `ariaLabelFn` * `averageCenter` * `batchSizeIE` * `calculator` * `clusterClass` * `enableRetinaIcons` * `gridSize` * `ignoreHidden` * `imageExtension` * `imagePath` * `imageSizes` * `maxZoom` * `minimumClusterSize` * `styles` * `title` * `zIndex` * `zoomOnClick` * `options` It is now recommended to customize the cluster using the `renderer` and `algorithm` inputs. Fixes angular#23695.
The marker clusterer component is currently based on the `@googlemaps/markerclustererplus` package which is deprecated. These changes rewrite the component to use `@googlemaps/markerclusterer` instead. BREAKING CHANGE: The new `@googlemaps/markerclusterer` API should be imported instead of the old one. Read more at: https://github.com/googlemaps/js-markerclusterer Furthermore, the new clustering package doesn't offer the same set of public APIs. As a result, the following inputs to the `MapMarkerClusterer` component have been removed: * `ariaLabelFn` * `averageCenter` * `batchSizeIE` * `calculator` * `clusterClass` * `enableRetinaIcons` * `gridSize` * `ignoreHidden` * `imageExtension` * `imagePath` * `imageSizes` * `maxZoom` * `minimumClusterSize` * `styles` * `title` * `zIndex` * `zoomOnClick` * `options` It is now recommended to customize the cluster using the `renderer` and `algorithm` inputs. Fixes angular#23695.
Does this issue still not consider for new updates? Is it possible to vote again? |
We really need to reconsider this issue. It took me too long to realize that I have to use the new Markerclusterer package, but add the script tag of the old markerclustererplus package to the head. Otherwise I get the markerclusterer class not found error. I'm not even sure it's a feature, seems more like a bug to me. |
I have same issue, Can we fix this issue ? |
Will this make the |
Any work in progress for this issue? |
I have the same problem, using the map-marker-clusterer component throw the error "class not found" that recommend to install the deprecated MarkerClustererPlus library... |
For me, the only version that is working is the following.
|
Thanks @rbalet I will try ! ![]() ![]() It work with @googlemaps/markerclusterer when creating clusters with the class MarkerClusterer itself but it won't work with the selector map-marker-clusterer |
For information - in my app I created a component based on the code in the draft PR #24853 updated for the latest version of the component and for Dynamic API loading. This seems to work well for me - but I make no guarantees. I have added an Input to tell the clusterer when the API is loaded - which I linked to the google map "loaded" output event. I am very sure that there are better ways of doing this but I don't have the time to find out. If I find the time - I might create a new PR based on this and someone can improve that. The component is in this gist: https://gist.github.com/runette/3cc43124bad49df69e28ae177cfdc8b9 the calling html is :
and
|
Support for Advanced Markers with Marker Clusterer is currently missing. This is related to #29187 and #23695.
|
Adds a new `MapMarkerClusterer` component that is based on the most up-to-date clustering library, and supports both regular and advanced markers. Fixes angular#23695.
Adds a new `MapMarkerClusterer` component that is based on the most up-to-date clustering library, and supports both regular and advanced markers. Fixes angular#23695.
Adds a new `MapMarkerClusterer` component that is based on the most up-to-date clustering library, and supports both regular and advanced markers. Fixes angular#23695.
Adds a new `MapMarkerClusterer` component that is based on the most up-to-date clustering library, and supports both regular and advanced markers. Fixes angular#23695.
Adds a new `MapMarkerClusterer` component that is based on the most up-to-date clustering library, and supports both regular and advanced markers. Fixes #23695.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Feature Description
I'd like to use the package https://www.npmjs.com/package/@googlemaps/markerclusterer instead of the old one https://www.npmjs.com/package/@googlemaps/markerclustererplus.
Use Case
It will be possible to use different algorithms, improve performance and more.
The text was updated successfully, but these errors were encountered: