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

fix(ivy): evaluate external declaration usages as dynamic #30247

Closed
wants to merge 1 commit into from

Conversation

JoostK
Copy link
Member

@JoostK JoostK commented May 2, 2019

Previously, ngtsc would fail to evaluate expressions that access properties
from e.g. the window object. This resulted in hard to debug error messages
as no indication on where the problem originated was present in the output.

This commit cleans up the handling of unknown property accesses, such that
evaluating such expressions no longer fail but instead result in a DynamicValue.

Fixes #30226

Previously, ngtsc would fail to evaluate expressions that access properties
from e.g. the `window` object. This resulted in hard to debug error messages
as no indication on where the problem originated was present in the output.

This commit cleans up the handling of unknown property accesses, such that
evaluating such expressions no longer fail but instead result in a `DynamicValue`.

Fixes angular#30226
@alxhub alxhub marked this pull request as ready for review May 16, 2019 15:57
@alxhub alxhub requested a review from a team as a code owner May 16, 2019 15:57
@alxhub
Copy link
Member

alxhub commented May 16, 2019

Presubmit

@alxhub alxhub added the action: merge The PR is ready for merge by the caretaker label May 16, 2019
@jasonaden jasonaden closed this in 1b613c3 May 16, 2019
@JoostK JoostK deleted the ngtsc-dynamic-values branch May 18, 2019 20:55
BioPhoton pushed a commit to BioPhoton/angular that referenced this pull request May 21, 2019
)

Previously, ngtsc would fail to evaluate expressions that access properties
from e.g. the `window` object. This resulted in hard to debug error messages
as no indication on where the problem originated was present in the output.

This commit cleans up the handling of unknown property accesses, such that
evaluating such expressions no longer fail but instead result in a `DynamicValue`.

Fixes angular#30226

PR Close angular#30247
@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 Sep 15, 2019
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 freq1: low risk: low target: major This PR is targeted for the next major release type: bug/fix workaround2: non-obvious
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IVY: ERROR in Invalid dot property access: undefined dot pathname
3 participants