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

Extension messing with html colorization #65

Closed
johnbwoodruff opened this issue Apr 5, 2017 · 2 comments · Fixed by #68
Closed

Extension messing with html colorization #65

johnbwoodruff opened this issue Apr 5, 2017 · 2 comments · Fixed by #68
Labels

Comments

@johnbwoodruff
Copy link

After installing this extension, my html element colorization has been messed up. See screenshot below.

screen shot 2017-04-05 at 10 24 46 am

I uninstalled the extension to make sure it was this extension, and the colorization went back to how it should be, shown below:

screen shot 2017-04-05 at 10 27 55 am

Upon re-installing, the colorization was messed up again.

@chuckjaz chuckjaz added the bug label Apr 5, 2017
@chuckjaz
Copy link
Contributor

chuckjaz commented Apr 5, 2017

It appears the grammar I have is messing with the html. I thought it would only add it if you used one of the extensions I registered. I will remove this in the next release as it is not necessary.

chuckjaz added a commit to chuckjaz/vscode-ng-language-service that referenced this issue Apr 5, 2017
Delegates to the built in html syntax.

Fixes angular#65
chuckjaz added a commit that referenced this issue Apr 5, 2017
Delegates to the built in html syntax.

Fixes #65
@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 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants