Clarify URL requirements #94
Conversation
|
Thanks for your suggestions so far. I expanded the text to be more explicit about the aspects you mentioned. While i do think the spec should be precise, i would rather explain things a bit more in depth than to aim for maximum conciseness. |
Co-authored-by: Gabriel McAdams <ghmcadams@users.noreply.github.com>
README.md
Outdated
| at this URL. Other protocols may also use that URL. | ||
| A GraphQL over HTTP compliant server MUST designate at least one URL that handles GraphQL requests. | ||
|
|
||
| All GraphQL operations that are available in a schema MUST be available on all URLs that are designated to it. |
There was a problem hiding this comment.
| All GraphQL operations that are available in a schema MUST be available on all URLs that are designated to it. | |
| All Queries and Mutations that are available in a schema MUST be available on all URLs that are designated to it. |
There was a problem hiding this comment.
What about subscriptions?
There was a problem hiding this comment.
Subscriptions often have some kind of redirection going on where multiple servers are involved. We might specify that in the future, but don't have a clear answer now.
- No promises on subscriptions for now - Introspection determines the schema
|
I incorporated feedback from the comments and the last working group meeting. If there is nothing seriously wrong, we can merge this for now to allow fine-grained iteration later. |
|
I figured we can just merge for now and take any future modifications in a future PR. |
Relates to the discussion in #91
@ghmcadams @ralfhandl