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(language-service): use host.error() instead of console.error() #34114

Closed
wants to merge 1 commit into from

Conversation

@kyliau
Copy link
Member

kyliau commented Nov 28, 2019

host.error() would log to file, and makes error messages much easier
to inspect because entries are time-stamped.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

`host.error()` would log to file, and makes error messages much easier
to inspect because entries are time-stamped.
@kyliau kyliau requested a review from ayazhafiz Nov 28, 2019
@kyliau kyliau requested a review from angular/tools-language-service as a code owner Nov 28, 2019
@ngbot ngbot bot added this to the needsTriage milestone Nov 28, 2019
@googlebot googlebot added the cla: yes label Nov 28, 2019
@mhevery mhevery closed this in 99320e1 Dec 2, 2019
mhevery added a commit that referenced this pull request Dec 2, 2019
…34114)

`host.error()` would log to file, and makes error messages much easier
to inspect because entries are time-stamped.

PR Close #34114
@kyliau kyliau deleted the kyliau:logImpossibleState branch Dec 17, 2019
@angular-automatic-lock-bot

This comment has been minimized.

Copy link

angular-automatic-lock-bot bot commented Jan 17, 2020

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 Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.