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
It's great to have an extensive example containing the concepts mentioned in the docs (Schema, Resolvers, Models, and Connectors). However, they're gone. It's about the quote below. Can we get them back?
Separate business logic from the schema. As Dan Schafer covered in his talk, GraphQL at Facebook, it's a good idea to treat GraphQL as a thin API and routing layer. This means that your actual business logic, permissions, and other concerns should not be part of your GraphQL schema. For large apps, we suggest splitting your GraphQL server code into 4 components: Schema, Resolvers, Models, and Connectors, which each handle a specific part of the work. You can see this in action in the server part of our GitHunt example app.
Source: https://github.com/apollographql/graphql-tools/blob/master/docs/source/index.mdx
The text was updated successfully, but these errors were encountered:
It's great to have an extensive example containing the concepts mentioned in the docs (Schema, Resolvers, Models, and Connectors). However, they're gone. It's about the quote below. Can we get them back?
The text was updated successfully, but these errors were encountered: