.yml files are ignored

[giovannicandido]

Using it with ansible, all .yml files has no syntax highlight
Renaming file to .yaml enables but is not compeling to rename all my files.

[JPinkney]

I've just tested this out using kubernetes schema and it works fine for me.

What ansible schema are you using and how are you setting it?

[giovannicandido]

Kubernetes works fine. But treats all non kuberntes as not being yaml files, unless renamed to .yaml

[giovannicandido]

I test in Windows and is ok. Problem is on Ubuntu Linux.

[giovannicandido]

The highlight is not working on folders:
roles
playbooks

This video show the behaviour: https://1drv.ms/v/s!AoHvV-Rb6N9QgoJ4ulk8Z7RUq2kCUg

[JPinkney]

Ah, thats such weird behaviour. I'll look into it and fix it for the next release.

[timm088]

Hrmm, not sure if related, but in my case, when using the 'comment' shortcut in .yaml files, i now get /* my thing */ .. i would be expecting # mything

New behaviour, does not occur in .yml files

Looks like i can force this in files.associations in settings, likely not related to the vscode-yaml addon, add behaviour though

[JPinkney]

Upon examination again I think that this isn't vscode-yaml, it looks like for some reason the .yml file is not getting registered as the yaml file type when opened. Though I'm not entirely why it isn't registering shrugs

[nomoresecrets]

had the same issue with *.yml files not being recognized as "Yaml" filetype, Check your settings (user, directory and workspace) for "files.associations" settings.

[JPinkney]

@nomoresecrets In your case did one of your plugins associate yml files with some other type? It looks like the vscode-ansible extension for example associates *.yml files with ansible (https://github.com/VSChina/vscode-ansible#usage) and i'm guessing that overrides the default association with yaml

[nomoresecrets]

yeah, I had manually set the association to "ansible" in all three settings files which drove me crazy b/c I didn't know you can have three different files^^

[Morriz]

Can we please get a fix for this simple problem?

[JPinkney]

Re-examining the problem, it looks like the filetype wasn't set to YAML it was set to plaintext (you can see it in the bottom right of the video when you open up one of the files that weren't highlighted) and that was the cause of this issue.

Both .yml and .yaml files should automatically associate to the YAML filetype and if they aren't it ends up as an issue with vscode itself, not with this extension so I'm going to close this.