Skip to content

fix: Check language service is not already disabled #423

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

Merged
merged 1 commit into from
Oct 18, 2019

Conversation

kyliau
Copy link
Contributor

@kyliau kyliau commented Oct 18, 2019

When making the check to determine if a project is Angular, it could be
the case that the language service is already disabled. This happens
when there are files in the project that exceeded limit.

This PR fixes the issue by first checking if the language service is
already disabled. Also added much more information to the logs to help
users diagnose the problem. Messages are logged to both remote console
(vscode) and file so that the former could inform users in their editor,
and the latter makes it much easier to correlate the sequence of events
in both TypeScript and Angular.

Related: #416

When making the check to determine if a project is Angular, it could be
the case that the language service is already disabled. This happens
when there are files in the project that exceeded limit.

This PR fixes the issue by first checking if the language service is
already disabled. Also added much more information to the logs to help
users diagnose the problem. Messages are logged to both remote console
(vscode) and file so that the former could inform users in their editor,
and the latter makes it much easier to correlate the sequence of events
in both TypeScript and Angular.

Related: angular#416
@kyliau kyliau merged commit d45ba15 into angular:master Oct 18, 2019
@kyliau kyliau deleted the disable-angular branch October 18, 2019 19:38
@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 Feb 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants