Skip to content

fix(google-maps): incorrect variable access for server-side rendering check #19166

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

Merged
merged 1 commit into from
Apr 24, 2020

Conversation

devversion
Copy link
Member

We added a SSR check to the google-maps window info directive, but when
this PR landed in the patch branch, the variable names no longer matched.

The variable for the _infoWindow has been made public with 3e00f4c, but
this change did not land in the patch branch as it targets a next minor release.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 24, 2020
… check

We added a SSR check to the google-maps window info directive, but when
this PR landed in the patch branch, the variable names no longer
matched. The variable for the `_infoWindow` has been made public
with 3e00f4c, but this change did not
land in the patch branch as it targets a next minor release.
@devversion devversion force-pushed the fix/patch-branch-map-info branch from b467469 to 8f1b01d Compare April 24, 2020 16:01
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added lgtm action: merge The PR is ready for merge by the caretaker labels Apr 24, 2020
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added the target: patch This PR is targeted for the next patch release label Apr 24, 2020
@jelbourn jelbourn merged commit b5864ca into angular:9.2.x Apr 24, 2020
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators May 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants