Use HTTPS for external URLs where applicable #217
Conversation
There was a problem hiding this comment.
Thanks for doing this!
The URLs without a path component all redirect to remove the trailing "/" so I'd prefer not to have it on those URLs. It's fine on the others.
Other than that two very minor nitpicks- if you'd prefer not to update the PR I can change them while merging it, but I prefer to let people reply rather than just dong that.
| - [JSONForms (jsonforms.io)](http://jsonforms.io) (EclipseSource) (MIT) | ||
| - [Jsonary](http://jsonary.com/) (MIT) | ||
| - [JSONForms (jsonforms.io)](https://jsonforms.io/) (EclipseSource) (MIT) | ||
| - [Jsonary](https://github.com/jsonary-js/) (MIT) |
There was a problem hiding this comment.
This should be https://github.com/jsonary-js/jsonary, not sure why the redirect of the old site went where it did.
| @@ -47,7 +47,7 @@ _If you are accessing the above meta-schema links **from a web browser**, you wi | |||
| Migrating from older drafts | |||
| ------------- | |||
|
|
|||
| The release notes discuss the changes impacting users and implementors: | |||
There was a problem hiding this comment.
Both spellings are correct, and I'm sure we use "implementors" elsewhere so I'd prefer not to change it.
|
Hmm... looks like we're already inconsistent on trailing slashes so I'll just merge as-is and sort it out later. |
No description provided.