vscode-ansible: No fallback to syntax-check when ansible-lint shows invalid yaml

Problem

When I’m working on ansible roles in vscode, and I have autosave enabled after a relatively short delay (like 1 second), ansible-lint get’s triggered before I’m actually done with my change.

This results in 2 notifications:

The error is about invalid yaml content, which is true - in that moment.

Solution

There is no need to fall back to ansible syntax-check if a usable ansible-lint is in place. Imo, a fallback should only happen if there’s either no ansible-lint, or the installed one can’t be used for whatever reason.

Instead of having 2 notifications, I’d prefer to have a more silent message, for example in the status bar telling me about broken yaml.

Alternatives

No response

Additional context

No response