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

Incorrect highlighting when { } are used inside YAML literal style #18

Open
Tracked by #1
aeschli opened this issue Nov 1, 2016 · 2 comments
Open
Tracked by #1

Comments

@aeschli
Copy link

aeschli commented Nov 1, 2016

From @ivanz on October 31, 2016 10:43

  • VSCode Version: 1.6.1
  • OS Version: Windows 10

Having issues with the highlighting of some AWS CloudFormation YAML templates which have some jsons fragments in YAML literal. Seems the { } may be tripping over the highlighting. Note how on the screenshot the highlighting stops working after the Bla: block.

image

Bla:
  - |
  {
    "jsonStuff": {
      "${something}": {
        "bla1":"sdfgsd",
        "bla1":"${asdf}"
        "bla1":"$[asdf]"
      }
    }
  }
this: is
broken: '000600'

Copied from original issue: microsoft/vscode#14753

@aeschli
Copy link
Author

aeschli commented Nov 1, 2016

Bla:
  - 
  {
    "jsonStuff": {
      "${something}": {
        "bla1":"sd",
        "bal2":"${asdf}",
        "bla3":"$[asdf]"
      }
    }
  }
this: is,

Seems to work with spaces after the colons

@cmeury
Copy link

cmeury commented Mar 22, 2018

Just encountered this as well (microsoft/monaco-editor#786) when editing helmfiles with VSCode.

infininight pushed a commit that referenced this issue May 4, 2018
While `\p{XDigit}` works, alternate regex engines might interpret it
according to UTS #18, which contains more than just the ASCII
characters, or not even implement it at all.

The YAML spec only contains the ASCII characters, see here:

http://yaml.org/spec/1.2/spec.html#id2775468
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants