-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Consider moving emmet completion to html completion provider in the html extension #28545
Comments
@ramya-rao-a I wasn't. It worked when I first pressed tab in my IDE. I just tried right now, It doesn't work with or without |
Ah! nice catch In the old emmet mode, https://github.com/Microsoft/vscode/blob/0117f311aa61d1af3018ee0749702dd5e5691738/src/vs/workbench/parts/emmet/electron-browser/editorAccessor.ts#L264 ensures This doesnt happen in the new model. Will look into it, thanks for reporting! |
Please read #28286 (comment) |
Note to verifier:
|
@ramya-rao-a now that the issue is fix, what should I do to have emmet in my hbs templates ? I tried: {
"emmet.includeLanguages": {
"hbs": "html",
"handlebars": "html",
"handlebar": "html"
}
} but it just doesn't autocomplete in my file (using 1.14.0). |
set |
It worked, thank you! |
@ramya-rao-a that configuration: It's just a patch but it should not be a solution. Because if you do this affects other files where suggestions should not appear. |
Good point Since html completion provider from the in-built html extension works for handlebars files as well, the best solution would be to move the emmet completion provider for html to the html extension. That way you will get completions at the right (html) places in the file. |
This last comment seems to me a better solution ;) Thank you! |
Update: Most of the required work is done. See #41652 |
This move will be reverted in the April milestone Keeping emmet html completions in html extension keeps us in a weird hybrid state of having one kind of completions coming from emmet and another from another built-in extension. The only advantage of keeping emmet inside html extensions was the ability to get css emmet completions inside style attributes which can be achieved in other ways when emmet completions move back to the emmet extension. See 79a2512 So, reverting the move of emmet html completions from html extension with c314388 |
Steps to Reproduce:
"emmet.useNewEmmet": true
to you settingsfile.hbs
div.foo
)expected content
actual content
this issue seems to be related to #28503.
The text was updated successfully, but these errors were encountered: