Add jinja-yml support for YAML json schemas.

[ImadYIdrissi]

Add jinja-yml support for YAML json schemas.

Autocomplete and JSON schema works correctly for YAML file association but not for Jinja-yml

Describe the solution you would like

When using this JSON schema with my YML files,

    "yaml.schemas": {
        "https://raw.githubusercontent.com/dbt-labs/dbt-jsonschema/main/schemas/latest/dbt_yml_files-latest.json": [
            "/**/*.yml",
            "!profiles.yml",
            "!dbt_project.yml",
            "!packages.yml",
            "!selectors.yml",
            "!profile_template.yml",
            "!package-lock.yml"
        ],
        "https://raw.githubusercontent.com/dbt-labs/dbt-jsonschema/main/schemas/latest/dbt_project-latest.json": [
            "dbt_project.yml"
        ],
        "https://raw.githubusercontent.com/dbt-labs/dbt-jsonschema/main/schemas/latest/selectors-latest.json": [
            "selectors.yml"
        ],
        "https://raw.githubusercontent.com/dbt-labs/dbt-jsonschema/main/schemas/latest/packages-latest.json": [
            "packages.yml"
        ]
    },

it is correctly integrated

When trying to do the same with jinja-yaml, it isn't available.

In fact I think it kind of crashes the extension. See this issue.

[edwardfung123]

I share the exact same use case. I have to admit that it is kind of a rare use to run jinja in a yaml file...

I think the main reason it does not work is because this YAML validation extension is registered to handle one language namely yaml. But jinja-yaml is considered as another language.

Perhaps just need to add jinja-yaml to this line here.

For example:

 const clientOptions: LanguageClientOptions = {
    // Register the server for on disk and newly created YAML documents
    documentSelector: [{ language: 'yaml' }, { language: 'dockercompose' }, { language: 'jinja-yaml' }, { pattern: '*.y(a)ml' }],
    synchronize: {

[ccostello97]

Same here. This would be great to have

[onedr0p]

Would love this too!

[agross]

I have to admit that it is kind of a rare use to run jinja in a yaml file...

Not when you use Ansible a lot, which coincidentally is also a Red Hat product.

[usipetic]

I have to admit that it is kind of a rare use to run jinja in a yaml file...

It's not rare at all. Ansible uses it, while Home Assistant is basically built on this mix.

[datho7561]

I think that you should be able to use the extension with files labelled as jinja-yaml in the prerelease version of the extension. (It was fixed in #1179 hopefully). However, I'm guessing if there's any actual Jinja templating in the file, the YAML parser will fail to parse the file.