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(compiler): correctly detect when to serialze summary metadata #20668

Closed
wants to merge 1 commit into from

Conversation

chuckjaz
Copy link
Contributor

The change to improve error messages broke the summary serialization
of summaries.

PR Type

What kind of change does this PR introduce?

[x] Bugfix

What is the current behavior?

Serialization of summaries was broken by change to improve reflector errors. It incorrectly dropped calls that were previously supported.

What is the new behavior?

The calls previously dropped are now correctly serialized.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

The change to improve error messages broke the summary serialization
of summaries.
@mary-poppins
Copy link

You can preview fd8d211 at https://pr20668-fd8d211.ngbuilds.io/.

@chuckjaz chuckjaz added area: core Issues related to the framework runtime action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release type: bug/fix labels Nov 28, 2017
@mhevery mhevery closed this in 8bb42df Nov 29, 2017
wKoza pushed a commit to wKoza/angular that referenced this pull request Dec 2, 2017
…gular#20668)

The change to improve error messages broke the summary serialization
of summaries.

PR Close angular#20668
@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 12, 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: major This PR is targeted for the next major release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants