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.

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

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

mskacelik
Copy link
Contributor

/cc @jmartisk

@@ -63,7 +63,7 @@ type User {
}
```

And you will can send such request
And you can send such a GraphQL request
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
And you can send such a GraphQL request
And you can send GraphQL request like

@@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

@@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.


> [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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> 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.


> [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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> [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.

@jmartisk jmartisk merged commit 45497d6 into smallrye:main Oct 9, 2024
5 checks passed
@mskacelik mskacelik deleted the smaller-fixes branch October 9, 2024 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants