Relay Modern: Simpler, faster, more extensible

Re:Relay Modern: Simpler, faster, more extensible by josephsavona on Tuesday April 18, 2017 @06:47PM (#14143726)

Thanks for the feedback!

> but there's no mention of subscriptions or client-side state control

The blog post didn't cover all the new features, but both of these use-cases are supported in Relay Modern - https://facebook.github.io/relay/docs/new-in-relay-modern.ht...

GraphQL Subscriptions are supported: applications must inject a network layer that provides support for connecting to the server and receiving subscription updates. Local state is supported via client-only extensions to the schema, combined with an imperative update API. More docs coming soon :-)

[ Parent | on HN ]

Re:Relay Modern: Simpler, faster, more extensible by aj0strow on Thursday April 20, 2017 @04:01PM (#14160300)

I read architecture.md in the runtime package and it looks perfect for binding websocket updates into components. I was really hoping for the following example:

* create a stand-alone relay store

* query and subscribe to changes, print to console

* imperatively push updated records into store

* see updated data in console

I assume this is possible, but maybe it's not? Or you need a graphql server or container component?

[ Parent | on HN ]

Re:Relay Modern: Simpler, faster, more extensible by djmashko2 on Tuesday April 18, 2017 @07:05PM (#14143845)

I'm excited to build an example with Relay Modern and the websocket subscriptions transport, should be really cool!

[ Parent | on HN ]

Re:Relay Modern: Simpler, faster, more extensible by voxmatt on Tuesday April 18, 2017 @08:10PM (#14144293)

Awesome!

[ Parent | on HN ]