You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah unfortunately there are quite a few schemas like this. I think I partially wrote a script in the maintenance task that checked for 404's (some responses expectedly return 301 unauthorized), but haven't replaced most of them. Ideally, I think the line with that URL should be blamed, and a comment should be added to the original PR (possibly automatically), when the route 404s (asking to update it). And if the URL points to a schema in a repository with very few stars, maybe even a PR that automatically removes it.
Only checking 404 is not enough though imho.
As I said, some URLs are valid but provide non-sense like an HTML page that displays the schema instead of the schema.
301 are redirects, so if you really meant 301, not 401, those should be followed during a check instead of ignored.
If it indeed were 401, I'm wondering whether non-public schemas should be part of the schemastore catalog. 🤷♂️
Area with issue?
JSON Schema
✔️ Expected Behavior
No invalid URLs in the catalog
❌ Actual Behavior
Invalid URLs in the catalog.
I did a quick CLI validation using
YAML or JSON file that does not work.
IDE or code editor.
None
Are you making a PR for this?
No, someone else must create the PR.
The text was updated successfully, but these errors were encountered: