YAML false positives

[notpeter]

I wanted to duplicate this report this here:

• Yaml custom tags, unresolved tags zed-industries/zed#18013

I found that the Docker Compose extension was the cause of the Unresolved Tag warnings. When I uninstalled the extension, they disappeared (using your test repo). The extension registers its own language server for YAML files. I re-installed the extension, but I disabled its language server it in my project settings:

    "languages": {
        "YAML": {
            "language_servers": ["yaml-language-server", "!docker-compose"]
        }
    },

Ultimately, the issue seems to be with other extensions registering language servers for YAML files and not providing a way to register custom tags.

I think the appropriate workaround is for the zed docker compose extension to register a new language Docker Compose instead of adding itself as a language server for YAML. Sadly path_suffixes in config.toml does not support globbing so currently it it could only be path_suffixes = ["docker-compose.yml", "docker-compose.yaml"] but users could manually specify globs via file_types in their zed user/project setting.json.

[lnay]

An extra benefit to having a new language Docker Compose would be to include a tasks.json and runnables.scm to allow users to docker compose run ... a service by just clicking on a runnable next to the service in the file.

[lnay]

@notpeter I see that it is possible to define a language which uses a grammar not specified in the same extension:

name = "Docker Compose"
grammar = "yaml"
path_suffixes = [
    "docker-compose.yml",
    "docker-compose.yaml",
    "compose.yaml",
    "compose.yml",
]
line_comments = ["# "]

Can highlights also be delegated to another language?

[notpeter]

Can highlights also be delegated to another language?

I don't believe so. I think you'd have to duplicate the scm files to your language extension.

[notpeter]

Note, this can also trigger errors with multi-document YAML files as reported here:

• Multiple documents in one yaml file zed-industries/zed#12122

Source contains multiple documents; please use YAML.parseAllDocuments() at line 169, column 1: (MULTIPLE_DOCS)

[oo00spy00oo]

Note, this can also trigger errors with multi-document YAML files as reported here:

• Multiple documents in one yaml file zed-industries/zed#12122

Source contains multiple documents; please use YAML.parseAllDocuments() at line 169, column 1: (MULTIPLE_DOCS)

Yes, the same issue with me. I must uninstall this Zed extension and keep waiting the next release!

[lnay]

@oo00spy00oo building commit 38a6573 as a dev extension works, but unfortunately it looks like there's an issue getting these changes through the zed extension release pipeline.

[dwt]

Is there anything I can do to help getting these changes tested and into zed? I just had to uninstall the docker compose plugin again because of the multiple document yaml issue.