Updates schemastore endpoint - #828
Open
konn wants to merge 1 commit into
Open
Conversation
|
FYI - the project seems to be dead (#715 (comment)) - so I doubt this will be merged. It's probably better to switch to tombi |
Author
|
@denysvitali-kaiko Oh, I didn't notice that. Thank you for your note! Meanwhile, I let this PR just as-is. |
|
The change proposed by this PR has been effectively applied as of 08f343b 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It seems that Schema Store recently changes their API endpoint to www.schemastore.org, instead of old json.schemastore.org for some reason. For example, although I could not find any actual discussion or announcement, this is stated here: microsoft/vscode#254689.
It seems that json.* subdomain had lived for some duration, but it starts to fail to serve reliably, and results in unexpected linting error.
This PR aims at fixing this just by rewriting schemastore catalog url. I confirmed that this should work by adding following lines to
.taplo.toml: