Just wondering, any reason for not using value (or previously named inline) classes for ID? It could avoid a bunch of needless allocations...

hi 👋 you mean for exposing

ID

from a GraphQL Kotlin server? I am unsure whether reflections would work with inline classes

Yes, I do. It could be you're right about reflection though, I thought you didn't need reflection for that one... I guess this could be another advantage of using an annotation processor for the schema generation 😉. It just occured to me, since I find myself creating tons of IDs... also, why should the ID not be generic? Then you could use toString to convert it, since ids can come from Ints or Longs too...

as per the https://github.com/ExpediaGroup/graphql-kotlin/issues/317 by allowing different types it would complicate the input coercion rules (output as you said is easy)