graphql defer-stream-wg Discussions
Discussions
-
You must be logged in to vote -
You must be logged in to vote Pending in response for nested defers
open questionNeeds WG consensus -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Early execution with @defer, and why we shouldn't specify it
open questionNeeds WG consensus -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Large number of payloads can degrade server performance
open questionNeeds WG consensus -
You must be logged in to vote defer/stream payloads in the initial response
open questionNeeds WG consensus -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote subscription: Allow to multiplex subsequent payloads between events
resolved future-considerationCould potentially be a future spec proposal after the initial defer/stream spec lands -
You must be logged in to vote -
You must be logged in to vote -
You must be logged in to vote Consider allowing clients to set response priority with
future-consideration@defer(order: Int).Could potentially be a future spec proposal after the initial defer/stream spec lands -
You must be logged in to vote -
You must be logged in to vote "incremental" field - is it useful beyond incremental delivery?
future-considerationCould potentially be a future spec proposal after the initial defer/stream spec lands
