Skip to content

feat: add option to specify custom schema store #459

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

Merged
merged 3 commits into from
May 19, 2021
Merged

feat: add option to specify custom schema store #459

merged 3 commits into from
May 19, 2021

Conversation

catthehacker
Copy link
Contributor

What does this PR do?

Adds option to specify custom schema store schema

What issues does this PR fix or reference?

redhat-developer/vscode-yaml#294
redhat-developer/vscode-yaml#406

Is it tested? How?

This change is published here: https://www.npmjs.com/package/@hackercat/yaml-language-server (with few changes in tests and my own schema store mirror) since I've tested it few times with custom store and clearing cache.
I think that the change is fairly small and easy to review. I'd appreciate any pointers since I never had any experience (except JS) with NodeJS/TS/NPM/etc. before and this whole thing was hacked in few hours (90% of time trying to figure out how to build this whole thing with vscode-yaml extension, it was a lot of yarn this, yarn that, I've not run yarn test for vscode-yaml extension since vscode breaks on my Alpine machine with musl instead of glibc).

@coveralls
Copy link

coveralls commented May 13, 2021

Coverage Status

Coverage increased (+0.08%) to 79.711% when pulling 79ecf30 on catthehacker:cat/feat/custom-schema-store into 813e2ce on redhat-developer:master.

Copy link
Collaborator

@evidolob evidolob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for long response.
Could you also preference in vscode-yaml for schema store url?

@evidolob evidolob merged commit d7ad1a6 into redhat-developer:master May 19, 2021
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

Successfully merging this pull request may close these issues.

5 participants