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-cli): only use error collector when needed. #19912

Closed
wants to merge 1 commit into from

Conversation

chuckjaz
Copy link
Contributor

The error collector changes behavior of the metadata resolver
in ways that haven't been fully hardened. This changes limits
its use to the lazy route detection and the language service.

Issue: #19906

PR Type

What kind of change does this PR introduce?

[x] Bugfix

What is the current behavior?

Issue Number: #19906

Part of issue 19906 demonstrates that the compiler was loosing error messages.

What is the new behavior?

Reverted the error collector for use in the primary ngc code path, switching back to a single error reporting mechanism used prior to the change.

The multiple error reporting is deferred now till 5.1 which will allow us time to harden the compiler against the changes to the metadata collector implied by using the error collector.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

The error collector changes behavior of the metadata resolver
in ways that haven't been fully hardened. This changes limits
its use to the lazy route detection and the language service.

Issue: angular#19906
@tbosch tbosch 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 labels Oct 24, 2017
@mary-poppins
Copy link

You can preview 889bb2b at https://pr19912-889bb2b.ngbuilds.io/.

@matsko matsko closed this in 7bfeac7 Oct 24, 2017
matsko pushed a commit that referenced this pull request Oct 24, 2017
The error collector changes behavior of the metadata resolver
in ways that haven't been fully hardened. This changes limits
its use to the lazy route detection and the language service.

Issue: #19906

PR Close #19912
@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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants