Skip to content

Update SubscriptionFields to match directive values #162

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

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Update SubscriptionFields to match directive values #162

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
12 changes: 6 additions & 6 deletions modules/ROOT/pages/directives/schema-configuration/type-configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,11 +115,11 @@ This directive is used to limit subscription operations in the library.
[source, graphql, indent=0]
----
enum SubscriptionFields {
CREATE
UPDATE
DELETE
CREATE_RELATIONSHIP
DELETE_RELATIONSHIP
CREATED
UPDATED
DELETED
RELATIONSHIP_CREATED
RELATIONSHIP_DELETED
}

directive @subscription(events: [SubscriptionFields!]! = [CREATED, UPDATED, DELETED, RELATIONSHIP_CREATED, RELATIONSHIP_DELETED]) on OBJECT | SCHEMA
Expand Down Expand Up @@ -210,4 +210,4 @@ This way, instead of the wrongly generated `teches`, the type is properly writte
----

The same is applied to other operations such as `createTechs`.
However, keep in mind that database labels are not changed with this directive.
However, keep in mind that database labels are not changed with this directive.
Loading