Scalar can be decorated with an undeclared directive

[roaris]

The schema below raise an error. name is decorated with an undeclared directive.

type User {
    name: String! @undeclareddirective
}

panic: graphql: directive "undeclareddirective" not found

But, the schema below does not raise an error. scalar S is decorated with an undeclared directive.

scalar S @undeclareddirective

Is this a bug?
The same is true not only for scalar, but also for argument, interface, etc.
The two schemas below also do not raise errors.

type Query {
    hello(name: String! @undeclareddirective): String!
}

interface I @undeclareddirective {
    name: String!
}

[pavelnikolov]

As far as I remember this is expected behavior because otherwise it would be declared and not used.

…

Sent from my phone

On 22 Mar 2022, at 2:11, roaris ***@***.***> wrote:  The schema below raise an error. directive @mydirective on FIELD_DEFINITION type User { name: String! @nonexistentdirective } panic: graphql: directive "nonexistentdirective" not found But, the schema below does not raise an error. directive @mydirective on SCALAR scalar S @nonexistentdirective Is this a bug? The same is true not only for scalar, but also for argument, interface, etc. The two schemas below also do not raise errors. directive @mydirective on ARGUMENT_DEFINITION type Query { hello(name: String! @nonexistentdirective): String! } directive @mydirective on INTERFACE interface I @nonexistentdirective { name: String! } — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.