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
The page https://graphql.org/graphql-js/running-an-express-graphql-server/ introduces the Ruru dependency. Yet, it's not really explained. Later in the page, it is referred to as "Graph_i_QL", which is not its name but rather the name (I suppose) of the previous tool used in this documentation.
Hi, Ruru author here, and also contributor to GraphiQL. Ruru is a very thin wrapper around GraphiQL which adds a couple extensions and makes it easy to get started by giving you a string you can serve easily. GraphiQL used to be bundled with express-graphql, but that library is now deprecated in favour of graphql-http, which has declared bundling GraphiQL to be out of scope (a view I support). Since there’s not currently a super simple way to get GraphiQL itself running with graphql-http, we’re (temporarily?) recommending Ruru until we come up with a cleaner solution. Ruru itself was put together to go with PostGraphile and Grafast (a new execution engine for GraphQL) but I hope it will be useful beyond that.
The page https://graphql.org/graphql-js/running-an-express-graphql-server/ introduces the Ruru dependency. Yet, it's not really explained. Later in the page, it is referred to as "Graph_i_QL", which is not its name but rather the name (I suppose) of the previous tool used in this documentation.
By looking around, it seems that Ruru is pre-release, and there's not much information about it online.
Giving this situation, would you consider updating the page to explain a bit more what Ruru is, and why was it picked over GraphiQL?
The text was updated successfully, but these errors were encountered: