-
Notifications
You must be signed in to change notification settings - Fork 141
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
Cluster on route transition #10
Comments
Hi! I don't think it's related to cluster. This error is from mapbox-gl v0.43.0, (right now ngx-mapbox-gl only support the version 0.42.2 as set in I'll see how to handle that properly. Currently Angular call ngOnDestroy of the source first. Which was ok until mapbox-gl team decided to throw an error when a source is removed whereas some layers are using it (makes sense but tricky in ngx-mapbox-gl because I'm not sure how to ask Angular to destroy component in a custom order). (ref mapbox/mapbox-gl-js#5562) |
Interesting, I'll think on it too. Thanks for the quick response. |
I fixed this by adding a buffer of source and layer, and actually removing them almost right away (in the same VM turn) in a defined order. |
I have a similar issue I'm not sure how to solve:
When I change the address I'm getting the following error: |
I'm having the same issue as @HarelM with only difference that I'm using 'mgl-image-source' and changing the coordinates dynamically.
So after doing this in my component
it throws me the same errors |
When you transition to a new route with 1.0.0.beta.3 and you have a cluster on a geoJSON source the current behavior is to remove the source with results in
If feels like you have fixed this with the new cluster mechanism for beta.4 + but I haven't been able to test it yet.
The text was updated successfully, but these errors were encountered: