-
Notifications
You must be signed in to change notification settings - Fork 108
usage in Node.js without React #155
Comments
This is what I ended up with. Feel free to close this issue unless there is a preferred way to parse the response.
|
@tdfairbrother This particular project is a binding to react-apollo. though it contains binding to apollo-client, it's not focus on that front. so no way you can avoid react when using this. If all you want is to parse the response, you can use graphql-ppx directly |
I guess I missed the blurb |
This is indeed something, maybe we could split ApolloClient as a different binding which would be dependency to Reason React Apollo |
@tdfairbrother do you have any more details on how you did this? Maybe an example gist? Did your create something like a Fetcher component then pass your Query module to it? For anyone, are you using a separate graphql client in the same project when you dont need react for a specific query? Thanks for any guidance. |
@idkjs here is a complete example
|
That is super useful @tdfairbrother. Thank you for sharing. I was going to try something like this.
I have no idea if that would work or not... |
Issue Labels
How do I query and parse the response of a query without using the React Query component?
React components render to the dom and to strings (for SSR) whereas I just want query and have a parsed reason response that I can work with for a backend task.
I notice that the decoder functions are hidden inside a React component. Is there a way to hook into these?
This has been talked about in #124 and #71 but I don't see any specific answers to bypassing React.
I have tried...
The text was updated successfully, but these errors were encountered: