documentation -- schema relative path isn't clear

The readme says Your schema must be a relative path and not an absolute path Relative to what? The yaml file being edited? The settings.json file? (I have a project where my yaml is in one git repo, and the schema is in another git repo – so, need to traverse folder paths – would be nice to have an example to follow!

[JPinkney]

For some reason I thought that wouldn’t work but indeed it does! So it looks like its time for me to change the docs a bit 😄.

I was able to get it working by doing:

"yaml.schemas": {
        "file:///Users/joshpinkney/Documents/custom-tags/yaml-language-server/testing/composer.json": "/test2.yaml"
    }

[AckslD]

@nkakouros Sorry to write in a closed issue but was just wondering if this worked for you? When I specify a global schema it seems it’s applied to all files even if they don’t match glob. If it’s a relative to file or root then this does not happen. Have you perhaps seen something similar?