-
-
Notifications
You must be signed in to change notification settings - Fork 213
Conversation
This replaces these with HTML stubs that will use a meta refresh tag and canonical link to perform a redirect. If there's code out there assuming that these exist and are JSON, then that code will be confused by receiving HTML. Although we do say that you can't assume these things are actually hosted. Not sure this is what anyone had in mind, though.
Because some of it is weird, and when redirecting for the JSON files, getting HTML is surprising.
Deploy preview for condescending-hopper-c3ed30 ready! Built with commit 7d53bd2 https://deploy-preview-300--condescending-hopper-c3ed30.netlify.com |
This is an excellent example of why using the unversioned schema URI / path is a bad idea.
@Relequestual any idea why the Travis job is showing up as incomplete? It looks like it completed successfully when I click through to Details. |
The deployment on netlify works fine (and handles the JSON better, too!). |
@handrews Not a clue. I've triggered a rebuild. See if that fixes it =/ |
Why do you think I'm so keen we move to netlify? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I <3 Netlify PR previews!
@awwright any thoughts on this? @Relequestual approved it, if I don't hear from you after a couple more days I'll merge this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good way to handle this
This replaces these with HTML stubs that will use a meta refresh
tag and canonical link to perform a redirect.
If there's code out there assuming that these exist and are JSON,
then that code will be confused by receiving HTML. Although we do
say that you can't assume these things are actually hosted.
Not sure this is what anyone had in mind, though.
Also explain the redirects some in the template, because
some of it is weird, and when redirecting for the JSON
files, getting HTML is surprising.
Also, as an example of this problem, the tests of the examples
against the meta-schema were failing because they were using
the unversioned meta-schema, which of course no longer makes
sense as neither the examples nor the validator have been updated.