Skip to content

fix(compiler): handle undefined annotation metadata #23349

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

Closed
wants to merge 1 commit into from

Conversation

alxhub
Copy link
Member

@alxhub alxhub commented Apr 12, 2018

In certain cases seen in production, simplify() can returned
undefined when simplifying decorator metadata. This has proven tricky
to reproduce in an isolated test, but the fix is simple and low-risk:
don't attempt to spread an undefined set of annotations in the first
place.

Fixes #23310.

@mary-poppins
Copy link

You can preview 24928f1 at https://pr23349-24928f1.ngbuilds.io/.

In certain cases seen in production, simplify() can returned
undefined when simplifying decorator metadata. This has proven tricky
to reproduce in an isolated test, but the fix is simple and low-risk:
don't attempt to spread an undefined set of annotations in the first
place.
@mary-poppins
Copy link

You can preview 2893a06 at https://pr23349-2893a06.ngbuilds.io/.

@jasonaden jasonaden added the area: core Issues related to the framework runtime label Apr 13, 2018
@alxhub alxhub added action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release labels Apr 19, 2018
@vicb
Copy link
Contributor

vicb commented Apr 20, 2018

@alxhub I changed this for master & patch please let me know if this is ok.

@vicb vicb added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Apr 20, 2018
@vicb vicb closed this in ca776c5 Apr 20, 2018
vicb pushed a commit that referenced this pull request Apr 20, 2018
In certain cases seen in production, simplify() can returned
undefined when simplifying decorator metadata. This has proven tricky
to reproduce in an isolated test, but the fix is simple and low-risk:
don't attempt to spread an undefined set of annotations in the first
place.

PR Close #23349
sis0k0 added a commit to NativeScript/nativescript-angular that referenced this pull request Apr 24, 2018
sis0k0 added a commit to NativeScript/nativescript-angular that referenced this pull request Apr 27, 2018
sis0k0 added a commit to NativeScript/nativescript-angular that referenced this pull request Apr 27, 2018
@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 13, 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 area: core Issues related to the framework runtime cla: yes target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[6.0.0-rc.1+] NGC fails when using classes from tns-core-modules as injection tokens
6 participants