-
Notifications
You must be signed in to change notification settings - Fork 34
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
Angular-Maps not working in Angular 9 #127
Comments
We are trying to upgrade to Angular 9 and Bing Map is not even loading. |
Any updates on this yet? |
Also awaiting a response on this |
The team at least inform us if you are committed to working on this repo at all |
I've ended up forking this and fixing in my own repo. Just needed the (More like a hot fix though, I've not changed the dependencies to Angular 9.) |
Any news on my PR been merged in yet? Many thanks! |
What to do to run bingmaps in angular 9? @JoeMellon How you have implemented InitMapInstance? Pls give solution on this. I am also getting same error like krishtgkk. |
I forked this repo and added my fix to it and use that...needs the InitMapInstance function moving to AfterViewIniti lifecycle. See my PR in this repo for the fix. |
As in the title, angular-maps doesn't work with Angular 9
The reason is how the viewchild is resolved. If you use ViewChild or ContentChild, angular is updating the way they resolve these queries to give developers more control. You must now specify that change detection should run before results are set. Example: @ViewChild('foo', {static: false}) foo !: ElementRef;.
https://angular.io/guide/static-query-migration
The text was updated successfully, but these errors were encountered: