You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, first I would like to say that your extension is very handy.
The extension works flawlessly when directly typing the tagname: it considers what already has been written and then completes it with all missing symbols and characters.
But when you start typing with the < symbol (e.g. like this <tagName) the extension appears to have 2 problems, or are they intended features?
Considering VSCode 1.10.2
First problem:
When typing <tagName it doesn't present any possible snippets, at all. Unless you press Enter after selecting the tagName in the auto-complete list, then CTRL+Space, then, and only then, the snippet shows.
e.g.:
First attempt with CTRL+Space after typing <a, only the IDE a tag appears:
With no snippet option:
After selecting the Auto-complete a tag, and hitting CTRL+Space again, the snippet option finally appears:
Second problem:
Continuing the above process, after hitting Enter over the a snippet option:
The extension places the snippet, but it doesn't take the symbol < into consideration, leaving it, which I think it shouldn't.
The text was updated successfully, but these errors were encountered:
hello @tradeli ,
thanks for the details explanation.
firstly, I made this extension was vscode had very little support for html autocomplete. the extension in its basic format is just snippet list that the vscode snippet engine feeds the workflow when it thinks a match is possible, the extension contains no logic to be smart about when to appear or how to handle the pre or post characters. if you are seeing the extension's suggestions below the default vscode html suggestions I believe there is a switch to set in the settings to allow the extensions to precede the default language type suggestions, again this is not just for this extension, this is for all snippet type extensions.
I have had many people enquire about similar features you have referred to, as to be able to understand what is on the page and the extension should provide that, I have been thinking of making a full fledged html extension that handles all user needs with that regard I just haven't had time to do so.
Hi, first I would like to say that your extension is very handy.
The extension works flawlessly when directly typing the
tagname
: it considers what already has been written and then completes it with all missing symbols and characters.But when you start typing with the
<
symbol (e.g. like this<tagName
) the extension appears to have 2 problems, or are they intended features?Considering VSCode 1.10.2
First problem:
![print1](https://cloud.githubusercontent.com/assets/8575811/24055795/4c4f1fcc-0b20-11e7-8f0f-3c5d9875a6df.png)
![print2](https://cloud.githubusercontent.com/assets/8575811/24055853/77c6196c-0b20-11e7-9987-8027d452a8b0.png)
![print3](https://cloud.githubusercontent.com/assets/8575811/24055893/9da0029c-0b20-11e7-9160-c4b372b42347.png)
When typing
<tagName
it doesn't present any possible snippets, at all. Unless you press Enter after selecting thetagName
in the auto-complete list, then CTRL+Space, then, and only then, the snippet shows.e.g.:
First attempt with CTRL+Space after typing
<a
, only the IDEa
tag appears:With no snippet option:
After selecting the Auto-complete
a
tag, and hitting CTRL+Space again, the snippet option finally appears:Second problem:
![print4](https://cloud.githubusercontent.com/assets/8575811/24055942/d073ffe8-0b20-11e7-955b-3ad67d6f9336.png)
Continuing the above process, after hitting Enter over the
a
snippet option:The extension places the snippet, but it doesn't take the symbol
<
into consideration, leaving it, which I think it shouldn't.The text was updated successfully, but these errors were encountered: