Skip to content

Better wording in HTTP "targetHints" section #477

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 9, 2017
Merged

Better wording in HTTP "targetHints" section #477

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions jsonschema-hyperschema.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1378,8 +1378,10 @@ for varname in templateData:
similarly structured headers wherever possible.
</t>
<t>
No distinction is made between headers that may appear in responses to
different methods, such as HEAD vs OPTIONS.
Headers for all possible HTTP method responses all share "headerSchema".
In particular, both headers that appear in a HEAD response and those
that appear in an OPTIONS response can appear. No distinction is made
within "headerSchema" as to which method response contains which header.
</t>
<t>
It is RECOMMENDED that schema authors provide hints for the values of
Expand Down