Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: paragraph rewrite #2128

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: paragraph rewrite #2128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/docs/get-started.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ const mySchema = application.schema

Now that you have `Module`, `Application` and you got your `GraphQLSchema`, you need to make it available to consumption.

GraphQL-Modules allow you to do much more, like managing the lifecycle of your execution, encapsulate your HTTP request and more. To do that in the most optimal and flexible way, we need to wrap the GraphQL execution flow. Some GraphQL servers implementation allow this kind of flexibility, and some doesn't.
GraphQL-Modules allow you to do much more, like managing the lifecycle of your execution and encapsulating HTTP requests. The most optimal and flexible way to achieve this is by wrapping the GraphQL execution flow; which only some GraphQL server implementations allow.

_But we got you covered, and provided solution for all popular GraphQL server implementations._

Expand Down