redhat-developer / redhat-developer/vscode-yaml

Extension does not work in vscode-insider on macOS

Open
#563 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
829
Forks
260
Avg merge
5h 43m
Merged PRs (30d)
1

Description

Summary

Yaml extension does not seems to work, only suggestions I get while writing code is whatever is already written in the same file. when I do ctrl+space it says no suggestions on new file.

Relevant information

Installed the extension and then added following lines in my settings

"redhat.telemetry.enabled": false,
  "yaml.schemas": {
    "./schemas/ansible-galaxy.json": [
      "/Users/scpace/wsl2_ansible/**/*.yaml"
    ],
    "./schemas/ansible-inventory.json": [
      "/Users/scpace/wsl2_ansible/**/*.yaml"
    ],
    "./schemas/ansible-playbook.json": [
      "/Users/scpace/wsl2_ansible/**/*.yaml"
    ],
    "./schemas/ansible-role-2.9.json": [
      "/Users/scpace/wsl2_ansible/**/*.yaml"
    ]
  },
  "security.workspace.trust.untrustedFiles": "open"
}

also placed the schema files under following path.
image
Since this didn't work so in order to give it relative path I copied the schema files to following path too.
image

/Users/scpace/Library/Application Support/Code - Insiders/User/schemas

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the missing suggestions in VS Code Insiders on macOS with the reported yaml.schemas settings and the ansible-galaxy.json, ansible-inventory.json, ansible-playbook.json, and ansible-role-2.9.json files. Verify the behavior in a new YAML file with Ctrl+Space; the issue is done when schema-based suggestions work with the reported paths or the path limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.