Skip to content

relative urls to project root / expanding variables. #43

@runar-rkmedia

Description

@runar-rkmedia

Not sure if this belongs here, or on in jsonls, or perhaps somewhere else, but I thought I would ask.

If a .vscode/settings.json is provided with for instance:

{
  "json.schemas": [
    {
      "fileMatch": ["**/myapp.json"],
      "url": "./jsonschemas/myapp-config.json"
    }
  ]
}

The settings are picked up by neovim, but the path is incorrect:

Unable to load schema from '/./jsonschemas/my-appconfig.json': ENOENT: no such file or directory, open '/./config/myapp-config.json'. [768]

in vscode, this is treated as a path relative to the project root. Could this work the same way here? Alternatively, the URL could be set with ${workspaceFolder}/jsonschemas/myapp-config.json, where workspacefolder is expanded to the project root.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions