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
In fact, I've tried everything, the only thing left is to write directly to name :)
The situation is as follows, I'm trying to make it so that when I specify a directive object, they are drawn in the scheme. Now it does not work. According to the documentation @graphql-tools/utils, if the fields are in the field in the object "extensions.directives" - then they should be drawn, but it does not work, because I'm 10 hours running through the objects in search of the truth :(
I will be grateful for an answer, even if it is impossible to implement.
...
args: {
email: t.arg.string({
description: "Email address",
required: true,
directives: {
constraint: getConstraints(validateDisplayName),
/*
This object is in the schema, and should be rendered, but it just goes into ignore (maybe under the hood, just like rateLimit it works, but I need the schema to know about it (Primarily for Codegen on the client)).
*/
},
}),
password: t.arg.string({ description: "Password", required: true }),
},
...
The text was updated successfully, but these errors were encountered:
There was a decision in GraphQL a long time ago that basically resulted in the core schema printer being unable to print directives other than the built in directives like @deprecated and @OneOf
In fact, I've tried everything, the only thing left is to write directly to name :)
The situation is as follows, I'm trying to make it so that when I specify a directive object, they are drawn in the scheme. Now it does not work. According to the documentation @graphql-tools/utils, if the fields are in the field in the object "extensions.directives" - then they should be drawn, but it does not work, because I'm 10 hours running through the objects in search of the truth :(
I will be grateful for an answer, even if it is impossible to implement.
The text was updated successfully, but these errors were encountered: