You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed, although the tricky part is writing the backend code that converts an arbitrary GraphQL subscription to the appropriate Materialize SUBSCRIBE command while handling auth, etc.
One thing to note: GraphQL subscriptions aren't a standardized thing. In particular they don't offer any help with update framing—no specification of e.g. "this is how you represent a delete vs an insert vs an update." Every client and server has a different take on how to communicate updates. So we'd have to invent or repurpose one of the existing protocols for this.
this opens up a new question for me about how to better surface both connection-examples and demos repos in the docs to to make it much easier for someone to search something like “materialize graphql” and get to that code.
Related to #10 . It seems like GraphQL subscriptions and Materialize fit like hand in glove. We should add an example GraphQL API that allows end users to subscribe to views in Materialize.
The text was updated successfully, but these errors were encountered: