#Fix Syntax highlighting in Studio Code Server

1 messages · Page 1 of 1 (latest)

unborn latch
#

Is it possible for the syntax highlighter to recognize valid homeassistant values?

It's annoying to open my configuration.yaml and get red errors like unknown tag <!include_dir_merge_named> or unknown tag <!secret>

As best as I can tell those aren't actual problems, but makes me less confident when trying to debug other issues.

teal egret
#

of course. In this case, the issue has already been fixed and released, but hasn't yet been included in the VSCode addon that you're presumably using

unborn latch
#

Yeah that looks like the exact issue. Although that issue looks closed.

#

Although I wonder if that's not the add-on I'm using, since mine says I'm on version 5.19.3 but github says it's on version 2.1.0

teal egret
#

it was merged and released

unborn latch
teal egret
#

those are versions for different things

#

Looks like it went into v2.1 of the extension, and the extension version was bumped to 2.1 3 weeks ago

#

oh, as I thought earlier, there hasn't been a release since May

#

I don't think you can update the extension manually in the addon

unborn latch
#

Where are you seeing what extension version the addon is using?

#

keesschollaart.vscode-home-assistant#2.1.0
Oh.

#

So basically "Wait a bit and it should be fixed"

teal egret
#

next release, whenever that happens

#

I think Frenck is currently on vacation, so no timeline