Yeah I know but it seems to me that it's worthwhile to find out how to have a GraphQL client separate from React for React applications that require data to be pre-fetched on the server (node) but does not require server side rendering of that data. I have all of that setup so all i have to figure out what i need for a graphQL client on Node that doesnt depend on React and then i can run FB's GraphQL server example for serving data via GraphQL.
The isomorphic route is slightly different than the data pre-fetching scenario. In the latter i don't render the components on the server, just the HTML page skeleton with the initial data already embedded as variables. I don't really need to render any component on server. I will post what i figure out to this thread. Sent from my iPhone > On Jul 23, 2015, at 12:51 PM, Matt Ho <[email protected]> wrote: > > I would separate this out into two separate issues; an ismorphic node app and > a unified api. Graphql can help on the later, but it doesn't provide the > former. If you have the former already, switching to Graphql shouldn't be > that huge an effort methinks > > M > > -- > Note that posts from new members are moderated - please be patient with your > first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
