Optional
queryExposes the root query type nested one level down. This is helpful for Relay 1 which can only query top level fields if they are in a particular form. (live)
Optional
nodeThe root query type must be a Node
to work well with Relay 1 mutations. This just resolves to query
. (live)
Optional
nodeFetches an object given its globally unique ID
. (live)
Optional
favouritesReads and enables pagination through a set of Favourite
. (live)
Optional
levelsReads and enables pagination through a set of Level
. (live)
Optional
levelReads and enables pagination through a set of LevelItem
. (live)
Optional
levelReads and enables pagination through a set of LevelMetadatum
. (live)
Optional
levelReads and enables pagination through a set of LevelPoint
. (live)
Optional
levelReads and enables pagination through a set of LevelPointsHistory
. (live)
Optional
levelReads and enables pagination through a set of LevelRequest
. (live)
Optional
personalReads and enables pagination through a set of PersonalBestGlobal
. (live)
Optional
recordsReads and enables pagination through a set of Record
. (live)
Optional
recordReads and enables pagination through a set of RecordMedia
. (live)
Optional
usersReads and enables pagination through a set of User
. (live)
Optional
userReads and enables pagination through a set of UserPoint
. (live)
Optional
userReads and enables pagination through a set of UserPointsHistory
. (live)
Optional
versionsReads and enables pagination through a set of Version
. (live)
Optional
votesReads and enables pagination through a set of Vote
. (live)
Optional
worldReads and enables pagination through a set of WorldRecordGlobal
. (live)
Optional
favourite(live)
Optional
level(live)
Optional
level(live)
Optional
level(live)
Optional
level(live)
Optional
level(live)
Optional
level(live)
Optional
level(live)
Optional
personal(live)
Optional
record(live)
Optional
record(live)
Optional
record(live)
Optional
user(live)
Optional
user(live)
Optional
user(live)
Optional
version(live)
Optional
vote(live)
Optional
world(live)
Optional
zRetrieves filtered level items based on specified criteria. (live)
Optional
favouriteReads a single Favourite
using its globally unique ID
. (live)
Optional
levelReads a single Level
using its globally unique ID
. (live)
Optional
levelReads a single LevelItem
using its globally unique ID
. (live)
Optional
levelReads a single LevelMetadatum
using its globally unique ID
. (live)
Optional
levelReads a single LevelPoint
using its globally unique ID
. (live)
Optional
levelReads a single LevelPointsHistory
using its globally unique ID
. (live)
Optional
levelReads a single LevelRequest
using its globally unique ID
. (live)
Optional
personalReads a single PersonalBestGlobal
using its globally unique ID
. (live)
Optional
recordReads a single Record
using its globally unique ID
. (live)
Optional
recordReads a single RecordMedia
using its globally unique ID
. (live)
Optional
userReads a single User
using its globally unique ID
. (live)
Optional
userReads a single UserPoint
using its globally unique ID
. (live)
Optional
userReads a single UserPointsHistory
using its globally unique ID
. (live)
Optional
versionReads a single Version
using its globally unique ID
. (live)
Optional
voteReads a single Vote
using its globally unique ID
. (live)
Optional
worldReads a single WorldRecordGlobal
using its globally unique ID
. (live)
Optional
__Optional
__
The root subscription type: contains events and live queries you can subscribe to with the
subscription
operation.Live Queries
Live query fields are differentiated by containing
(live)
at the end of their description, they are added for each field in theQuery
type. When you subscribe to a live query field, the selection set will be evaluated and sent to the client, and then most things* that would cause the output of the selection set to change will trigger the selection set to be re-evaluated and the results to be re-sent to the client.(* Not everything: typically only changes to persisted data referenced by the query are detected, not computed fields.)
Live queries can be very expensive, so try and keep them small and focussed.
Events
Event fields will run their selection set when, and only when, the specified server-side event occurs. This makes them a lot more efficient than Live Queries, but it is still recommended that you keep payloads fairly small.