Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible syntax error #423

Closed
1 of 4 tasks
bapi25 opened this issue Feb 4, 2021 · 2 comments
Closed
1 of 4 tasks

ansible syntax error #423

bapi25 opened this issue Feb 4, 2021 · 2 comments

Comments

@bapi25
Copy link

bapi25 commented Feb 4, 2021

ansible syntax bad analyses

there is a surligned code which is correct for ansible but not for this extension vscode-yaml.
{
"resource": "../main.yml",
"owner": "generated_diagnostic_collection_name#1",
"severity": 8,
"message": "Incorrect type. Expected "string".",
"source": "yaml-schema: Ansible 2.9",
"startLineNumber": 31,
"startColumn": 7,
"endLineNumber": 34,
"endColumn": 3
}

example :

image

how can i leave this extension but deactivate this kind of check that is not relevant?

Thanks in advance

Expected Behavior

no warning or surligned text

Current Behavior

error message and surligned text in red
message": "Incorrect type. Expected "string".",

Steps to Reproduce

have a list in ansible module "debug" option msg instead of a simple string

Environment

  • Windows
  • Mac
  • Linux
  • other (please specify)
@ssbarnea
Copy link
Member

ssbarnea commented Feb 4, 2021

I am afraid that linting Ansible is bit outside the scope of YAML extension for multiple reasons including decision about when to use a schema or not and also about the schema itself.

That is why I initiated an extension that will aim to cover ansible bits, one that will reuse vscode-yaml: https://github.com/ansible-community/vscode-ansible -- Be warned that this is in very early stage and I am looking for others to join the effort, especially as my extension development skills are very low.

@gorkem
Copy link
Collaborator

gorkem commented Mar 6, 2022

Closing as Ansible extension is available on the marketplace and should handle further issues.

@gorkem gorkem closed this as completed Mar 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants