-
Notifications
You must be signed in to change notification settings - Fork 15
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
No Emmet expansion for same line template literals #4
Comments
@mblais I'll have to test this out once i am home. Glad you found it useful though :) |
@mblais I can't seem to reproduce this issue on latest VS, Could you please provide more details? |
Try it with your cursor at the end of a file. I just reinstalled it - I'm getting the inline HTML syntax coloring in a .js file, but still no emmet. My emmet is working in a .html file. |
@mblais Could you generate a file with the content that bugs? or record a quick gif. I really want to reproduce this to get it fixed. |
Literally anything - I just tried this with same result:
If you want to insert some debug info in the extension I'd be happy to send you the output. |
@mblais I can reproduce it now, For some reason, It's because you have the tilde on the same line. A temporary solution is to just add a new line so instead of
do
Anyways I'll try to fix this asap. |
Unfortunately that doesn't work either. |
I think I understand the problem: in order for emmet to work here, a couple things need to be true:
When I get all the conditions correct, it works :-) But honestly, how is a newbie supposed to guess these restrictions? |
@mblais I labeled this as a bug because, indeed, it doesn't have to be like this and this behavior is completely unexpected for the user. Problem is, this has to do more with how VSCode doesn't "officially" support embedded languages. |
I just installed the extension (thanks! :)
When I create an
html
inline string, the first tag I add does not get emmet-expanded - I see the emmet popup, but when I hit Enter, it disappears without substituting.After I manually enter a valid closed tag, all works fine following it.
The text was updated successfully, but these errors were encountered: