Schema suggestions not working for `meta/main.yml` files with Ansible language

[alisonlhart]

Summary

When a meta/main.yml file is identified as Ansible language, suggestions from the built-in JSON schema analyzer do not appear.
Changing the language to YAML makes the suggestions appear on the same file.

Example:
Ansible language, no suggestions for collections key:

Switched to YAML language, suggestions given for collections key:

Extension version

25.8.1

VS Code version

1.103

[PratikMane0112]

@alisonlhart, I am happy to take the issue under hacktoberfest'25 & work on it further, Can I proceed ?

[yangskyboxlabs]

AFAICT the plugin both under- and over-matches on what should be handled as ansible files to use with LSP, and what should be yaml using only schema validation.

My proposal would be to change the file association such that only role task and handler YAML files are associated with ansible.

Related: #1802

(I can trivially produce a PR for this, but I don't want to get in the way of any sponsored work for @PratikMane0112 )

[PratikMane0112]

@alisonlhart, after duplicating the issue locally, I think the issue occurs because :

• the main.yml file matches the Ansible language pattern defined in package.json
• VS Code's built-in YAML schema validation and suggestions are tied to the YAML language mode, not the Ansible language mode.
• the ansible extension doesn't provide schema suggestions for main.yml files when they're identified as Ansible language.

The fix can be either:

• adding schema support to the Ansible language server for main.yml files.
• excluding main.yml from Ansible language patterns so they remain as YAML
• integrating YAML schema validation into the Ansible language mode