Comments (3)
General concensus from Spec WG on the content-type is "don't bother getting it approved... yet". Just use it. You can tick that off, I'll be updating people at the next HTTP WG - see #78
from graphql-over-http.
I've used the following mission statement and shared with some leaders at GraphQL Foundation and asked about the process of legally migrating this into the GraphQL Foundation.
Provide a specification that allows GraphQL clients and servers with different implementations and technology stacks to interact freely over HTTP if both client and server are compliant
Will report what I hear back on that thread at the meeting on Tuesday, April 28.
from graphql-over-http.
I've drafted a PR that adds guidance around serialization format and content-type into the specification. This reflects some ideas that were surfaced in our last meeting and puts inserts into the spec our proposed content type, application/graphql+json
.
from graphql-over-http.
Related Issues (20)
- Next meeting: Thurs July 21st 17:00 UTC? HOT 12
- [2022-06-27] Incorporate David's and working group's feedback
- [2022-06-27] Contact Denis to discuss compatibility with websockets and SSE spec
- [2022-06-27] Check spec-md is working correctly and split the spec up into sections
- [2022-06-27] Go through the issues and close those that are not relevant any more
- [2022-06-27] Copy over relevant issue labels from main spec repo HOT 2
- [2022-06-27] Schedule a meeting after the July spec WG
- Spec references RFC7231 which is obsoleted HOT 4
- Response status code as `application/json` content HOT 5
- Clarify the use of HTTP GET and POST request HOT 2
- Status codes for unauthenticated OAuth errors HOT 1
- Optional query discussion HOT 13
- GraphQL request optional parameters HOT 2
- Kitchen sink HTTP requests HOT 3
- Allow non-UTF-8 encodings HOT 2
- What is well-formed response HOT 3
- Status codes 404 and 410 HOT 1
- Clarification for `Accept: */*` HOT 8
- Should we explicitly support `Content-Type: application/graphql`? HOT 13
- Should the query property really be required? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphql-over-http.