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
Website release causes HTTP requests to 301 redirect to HTTPS. One user has reported this causes a problem for one implementation (net.jimblackler.jsonschemafriend) which does not follow the redirect. - Question: Do we want to fix this? Should old meta-schemas be available on http only URLs? (We should be able to without huge effort if we want.) (OP filed an Issue with the implementation.)
We started discussing various topics including updating the Jason schema playground and sharing schemas.
The team discussed some steps to complete the roll-out of the new website including disabling GitHub pages and archiving repositories for the old website, the blog and Understanding JSON Schema.
They also addressed the problem of an implementation (net.jimblackler.jsonschemafriend) breaking due to HTTP to HTTPS redirect, and agreed that it exposed bugs that needed fixing. They debated whether to revert the implementation or fix the library, ultimately deciding to bundle the master schemas or stop doing schema validation.
The discussion revolved around a specific implementation that required calling a method called loadSchema to validate using a schema, which would automatically download the schema if it was not already in the schema store. They concluded that although it was a temporary solution, it was not ideal and should be modified to avoid the need for such a method.
Open Community Working Meeting 2023-10-02 - 14:00 PT
📺 See Recording
⏪ Go To Previous Meeting
Agenda:
Action items:
No action items has been captured.
Notes:
We started discussing various topics including updating the Jason schema playground and sharing schemas.
The team discussed some steps to complete the roll-out of the new website including disabling GitHub pages and archiving repositories for the old website, the blog and Understanding JSON Schema.
They also addressed the problem of an implementation (
net.jimblackler.jsonschemafriend
) breaking due to HTTP to HTTPS redirect, and agreed that it exposed bugs that needed fixing. They debated whether to revert the implementation or fix the library, ultimately deciding to bundle the master schemas or stop doing schema validation.The discussion revolved around a specific implementation that required calling a method called
loadSchema
to validate using a schema, which would automatically download the schema if it was not already in the schema store. They concluded that although it was a temporary solution, it was not ideal and should be modified to avoid the need for such a method.Attendees
The text was updated successfully, but these errors were encountered: