-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Invalid URLs in the catalog #4404
Comments
Yeah unfortunately there are quite a few schemas like this. I think I partially wrote a script in the Dupe of #2247 |
Only checking 404 is not enough though imho. 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. 🤷♂️ |
Yeah, I meant
Currently, the Tycho schema is. Currently, these are documented in the "maintenance" task (PR imminent) |
Ah, ok, for me the Tycho schema does not give a 401 but the whole hostname is not resolvable for me.
|
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: