Replace json.schemastore.org with www.schemastore.org - #866
Closed
palfrey wants to merge 1 commit into
Closed
Conversation
This was referenced May 5, 2026
Author
|
#828 does most of this as well |
|
The change proposed by this PR has been effectively applied as-is as of 08f343b. |
|
At the moment, However, visiting https://www.schemastore.org/api/json/catalog.json in a web browser returns a valid-looking JSON response. The older schema catalog suggested in #463 (comment) is no longer working for me either. It seems likely that |
AlexTMjugador
added a commit
to AlexTMjugador/dotfiles
that referenced
this pull request
Aug 7, 2026
Taplo is not really working properly anymore, and Tombi is the best maintained successor for it at the moment. See: tamasfe/taplo#866
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
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.
I've just hit #799 again which I believe is related to SchemaStore/schemastore#5621.
Advice from there was "Btw, everyone should use www. instead of json. subdomains for accessing anything on schemastore.org. If you have any hardcoded values pointing to json., then replace it now with www." which is what this PR does and it makes things work again