from Hacker News

GraphQL Live Queries with live directive

by tobase on 1/16/23, 7:03 PM with 11 comments

  • by satvikpendem on 1/16/23, 8:13 PM

    I love GraphQL, it makes generating types for any language very easy, with one schema, and you don't have to worry about the shape of the response on either the server or the client due to such types. If you don't need multiple clients and are using TypeScript, you could use trpc though (and with Rust I also know of rspc).

    This article is interesting, however it seems `@live` isn't part of the official specification. Also, you can use something like TanStack Query to synchronize server state, which works with GraphQL as well as regular REST, or you can use a GraphQL client directly like Apollo or urql, which also does the same syncing, so I'm not sure for what purpose this directive serves exactly. Maybe it's for languages that don't have a good server side syncing library?

  • by Emigre_ on 1/16/23, 8:58 PM

    The 'live queries' RFC in the GraphQL spec has been in strawman stage (RFC 0) for a while.

    https://github.com/graphql/graphql-spec/issues/386

  • by vlaaad on 1/16/23, 8:24 PM

    Huh, I've been thinking about a very similar service that does not require a dependency on GraphQL — https://poll2hook.com/

    You can define a query on any API, be it GraphQL or REST, and a jq query to extract events, and you are good to go. I wonder if this @live directive is implemented with polling?