-
Notifications
You must be signed in to change notification settings - Fork 93
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.
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
some small fixes (documentation/code) #2205
Conversation
docs/namespaces-on-server-side.md
Outdated
@@ -63,7 +63,7 @@ type User { | |||
} | |||
``` | |||
|
|||
And you will can send such request | |||
And you can send such a GraphQL request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And you can send such a GraphQL request | |
And you can send GraphQL request like |
docs/namespaces-on-server-side.md
Outdated
@@ -79,7 +79,7 @@ query { | |||
## Using @Name annotation (deprecated) | |||
> [NOTE] This feature may be removed in the future. | |||
|
|||
Does the same thing as @Namespace, the only difference is that there can only be one nesting level. | |||
It does the same thing as `@Namespace`; the only difference is that there can only be one nesting level. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does the same thing as `@Namespace`; the only difference is that there can only be one nesting level. | |
It does the same thing as `@Namespace`, the only difference is that there can only be one nesting level. |
docs/namespaces-on-server-side.md
Outdated
@@ -142,8 +141,8 @@ subscription { | |||
``` | |||
|
|||
There is currently no way around this problem. | |||
You must move subscriptions into a separate class that is not placed in a namespace. | |||
You must move subscriptions into a separate class that is not placed within the namespace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must move subscriptions into a separate class that is not placed within the namespace. | |
You must move subscriptions into a separate `@GraphQLApi` class that does not declare any namespace. |
docs/namespaces-on-server-side.md
Outdated
|
||
> [NOTE] | ||
> Be very careful when designing API with namespace. | ||
> And take into account all the features of working with mutations and subscriptions. | ||
> And consider all the features of working with mutations and subscriptions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> And consider all the features of working with mutations and subscriptions. | |
> And be aware of all the potential consequences when working with mutations and subscriptions. |
docs/typesafe-client-usage.md
Outdated
|
||
> [NOTE] You can only use one of the annotations - @Name or @Namespace over the GraphQLApi classes. | ||
> [NOTE] You can only use one of the annotations - `@Name` or `@Namespace` over the GraphQLApi classes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> [NOTE] You can only use one of the annotations - `@Name` or `@Namespace` over the GraphQLApi classes. | |
> [NOTE] You can only use one of the annotations - `@Name` or `@Namespace` on a `GraphClientQLApi` interface. |
740fc15
to
0bd1184
Compare
/cc @jmartisk