Skip to content
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

docs(maps): Describe how to get map instance from within component.ts to input to MapMarker, InfoWindow #24042

Open
SheldonHage opened this issue Dec 1, 2021 · 1 comment
Labels
area: google-maps docs This issue is related to documentation P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@SheldonHage
Copy link

Documentation Feedback

Currently the example docs rely on a single use case where the user interacts with the map and a (mapClick) event grabs the map instance and passes it back to a component.ts function. If a developer wishes to decorate a map with a marker or an info window before a user interacts with it, there is no map reference to use.

It appears that standard @ViewChild methods for obtaining a dom reference do not work with the angular google-maps component. We could use a good example of how to get the map reference.

Affected documentation page

https://github.com/angular/components/tree/master/src/google-maps/map-marker

@SheldonHage SheldonHage added docs This issue is related to documentation needs triage This issue needs to be triaged by the team labels Dec 1, 2021
@amysorto
Copy link
Contributor

It seems like this was fixed in #23856, I'll leave this issue open to update documentation

@amysorto amysorto added area: google-maps P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent and removed needs triage This issue needs to be triaged by the team labels Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: google-maps docs This issue is related to documentation P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

2 participants