Is that comma really necessary? Should it be there? Sorry if this is a dumb question / for any wasted time.

I always check for updates but I already got the latest update and still, the error shows up.
emmetExtensionsPath.trim is not a function

The jsx.enabled option should be allowed to override.

From: vuejs/vetur#2522

In v2.0.9, the doComplete return null when I input marginright.
In v2.1.2, the doComplete return marginright: | completion when I input marginright.

Is it a correct result?

As an example, for XSL files, cp should expand to <xsl:copy select="|" />, but right now it expands to <xsl:copy select="|">|</xsl:copy>.
This issue occurs for two reasons:

• In the snippets within expand-full.js, we have the mapping "cp": "xsl:copy[select]", without the / at the end. Therefore, the expander interprets the tag as one with content in between.
• Even if / is added to the end, the XSL content is interpreted as HTML and expands to <xsl:copy select="|">, which is not a valid self-closing tag within XSL.

The master branch at the moment is using version 0.5.10 of expand-abbreviation module with latest version of abbreviation and snippets module. See https://github.com/ramya-rao-a/expand-abbreviation/tree/0.5.10

We should move on to use the latest version of the expand-abbreviation module.

Hi,

Just want to know if there are any plan to publish releases rather then the tags, thanks!

We have upstream: https://github.com/emmetio/emmet/blob/master/src/config.ts#L353
Which we access in this repo in this function: https://github.com/microsoft/vscode-emmet-helper/blob/main/src/emmetHelper.ts#L399, which defaults the stylesheet syntax to use to CSS.

To look into: do we need to default the syntaxToUse to CSS?

See line: https://github.com/ramya-rao-a/vscode-emmet-helper/blob/master/src/emmetHelper.ts#L47

This is impossible to translate.

Replication steps:

1. Set the user setting emmet.showExpandedAbbreviation to never.
2. Install the VSCode extension Vetur: https://github.com/vuejs/vetur
3. Open a .vue file, in the CSS section type in flex-direction: col.
4. Notice that Emmet abbreviations still show up in the suggestions list.

Hopefully this makes sense. I'm referencing this issue: vuejs/vetur#412

Thanks!

The package.json declares "module": "./lib/esm/emmetHelper.js", but the esm folder is missing from the package since version 2.8.5

Either remove the module field if this is deliberate or adjust the build pipeline so that the esm version is built and published.

I don't know is it a bug?

Ref: vuejs/vetur#2742

I have installed a few extensions all of them give me this error message:
[Error - 13:17:48] Notification handler 'workspace/didChangeConfiguration' failed with message: emmetExtensionsPath.trim is not a function

I have tried to uninstall VS code and re-install it without any success, so my question is what is the problem and how do I get the extensions to work. One of them is the "Adonis JS, v1.0.2" extension.

Commonly used tags were whitelisted, so that not every word triggers emmet suggestions which can be noise.

Emmet itself doesn't manage a white list and so we need to do so.

Current support: ['div', 'span', 'p', 'b', 'i', 'body', 'html', 'ul', 'ol', 'li', 'head', 'script', 'h1', 'h2', 'h3', 'h4', 'h5', 'h6', 'section']

Should include:

• header
• footer

Use web pack to get a single file distribution of vscode-emmet-helper.

This will then free us from the need to use the umd version of the expand-abbreviation module.

Related: vuejs/vetur#656

Ideally, the helper library could take a list of tag definitions (similar to HTMLTagSpecification in https://github.com/Microsoft/vscode-html-languageservice/blob/master/src/parser/htmlTags.ts) and allow tag completion with those custom tags.

For example, if a definition for tag <my-component> is available and passed to the helper, the helper should provide completion for it for cases like

<my-comp|

I don't know if it's viable to pass through the list to doComplete each time, because the list could be huge. Some Vue UI library provides hundreds of custom tags (Quasar, Element).
A better approach might be having a stateful CompletionProvider class that exposes a method for adding tag definitions.

div{ foo (bar) baz } should expand to <div>foo (bar) baz</div>. But currently this does not work because it's considered an invalid expression due to the following code

Restricting ( and ) to be only next to >, +, * or ^ misses the case where ( or) are inside { and } that is in a text node.

Actual behavior:

Expected behavior (as seen on emmet's docs):

I'll be sending a PR soon!

I am unable to use VSCode for Emmet expansions since I need larger expansions which are able to be done in SublimeText. For example, tag#id$$$*400>some-thing{PLACEHOLDER_1}+some-thing-else{PLACEHOLDER_2}.

This is extremely useful for when parsing large datasets using a regex and inputting data in auto-numbered columns for XML data tables.

It would be nice to not have to keep SublimeText installed for this one small use case.

Description

Currently this repository does not have templates for different issues and PRs. I guess adding a few templates might be a good idea and would improve the overall contributor experience.

Solution

We can simply add a .github folder and put our templates there, that should make future additions of new templates easier. We can refer to the templates being used in the vscode repository.

I am having problems with expanding the expression below:

`md-content[layout="column"].md-padding>md-subheader.md-no-sticky>div[layout=row layout-align=left]>md-button.md-raised.md-primary[ng-click="$ctrl.add()"]`

expanding only processes the chunk:

div[layout=row layout-align=left]>md-button.md-raised.md-primary[ng-click="$ctrl.add()"]

By enabling strict true, we wouldn't have to deal with the fact that any function can return undefined without it showing up in the type signature.

However, many errors show up upon enabling this check, and it's not as high-pri as other issues, so I'm labelling this as a debt issue.

There are multiple abbreviations within https://docs.emmet.io/cheat-sheet/ that end in +, such as ul+.
The current implementation of the expansion algorithm does not allow these abbreviations to work, even if added to the list of snippets within expand-full.js.