Directive arguments support @GraphQLIgnore

Creating a new directive with an ignored field will prevent the schema from being generated when the ignored field type is not in the supported packages. Is there a way to prevent this behavior? It seems like a type that is only referred to in an ignored field should not break schema generation even if it is not in the supported packages.

Example in a directive:

@GraphQLDirective()
annotation class TestDirective(
        val value: String,
        @GraphQLIgnore
        val ignore: Array<KClass<*>> = [] 
)

Results in Caused by: com.expediagroup.graphql.exceptions.TypeNotSupportedException: Cannot convert kotlin.reflect.KClass<*> since it is not a valid GraphQL type or outside the supported packages [...]

Obviously something like kotlin.reflect should not be added to the supported packages and nothing representing KClass should be in the schema.

[smyrick]

@oatmeal-raisin From what I can tell there is no way to get the argument annotation information from a directive during schema generation unless you know the specific class type. So the best way to solve this is just with the hooks.

See the PR for more details https://github.com/ExpediaGroup/graphql-kotlin/pull/763

[oatmeal-raisin]

Thanks @smyrick and @dariuszkuc. I really appreciate how responsive your team is and I am looking forward to the enhancement. Are there any hooks I can take a look at that do something similar? I will need to both exclude the field and to prevent the type on that ignored field from causing an exception because it is not in the configured packages.