System-prefixed paths in yaml.schemas #751
-
I currently have the following in
which in a different computer is:
Note that the only difference is that my E.g. Does this setting support environment variables? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I don't think VSCode supports having env variables in settings: microsoft/vscode#2809 A workaround would be directly linking to the schema itself: https://bitbucket.org/atlassianlabs/atlascode/raw/4e9ef8faf727737cd9585bb01340117cd8236d44/resources/schemas/pipelines-schema.json |
Beta Was this translation helpful? Give feedback.
-
I am having the same issue while switching between Windows and Ubuntu. If the schema is updated regularly, hardcoding a link https://bitbucket.org/atlassianlabs/atlascode/raw/4e9ef8faf727737cd9585bb01340117cd8236d44/resources/schemas/pipelines-schema.json may pose problems. "yaml.schemas": [
{ "file:///{linux_path}/atlassian.atlascode-2.8.6/resources/schemas/pipelines-schema.json": "bitbucket-pipelines.yml" },
{ "file:///{windows_path}/atlassian.atlascode-2.8.6/resources/schemas/pipelines-schema.json": "bitbucket-pipelines.yml" },
] If on the other hand the schema does not change, setting the |
Beta Was this translation helpful? Give feedback.
I don't think VSCode supports having env variables in settings: microsoft/vscode#2809
A workaround would be directly linking to the schema itself: https://bitbucket.org/atlassianlabs/atlascode/raw/4e9ef8faf727737cd9585bb01340117cd8236d44/resources/schemas/pipelines-schema.json