Possible future package structure

Is your feature request related to a problem? Please describe. We would like to add more logic to the graphql kotlin library in the future to take advantage of running a full kotlin schema and maybe even sharing some of the core graphql packages with client libraries.

Describe the solution you’d like We should update the package path of the schema generator and prepare for having new packages

We may also want to update the path of graphql-kotlin-schema-generator to reserve the top level path for other things

Package Name	Package Path
graphql-kotlin-schema-generator	com.expediagroup.graphql.generator
graphql-kotlin-federation	com.expediagroup.graphql.federation
graphql-kotlin-spring-server	com.expediagroup.graphql.spring
graphql-kotlin-schema*	com.expediagroup.graphql.schema*
graphql-kotlin-server*	com.expediagroup.graphql.server*
graphql-kotlin-client*	com.expediagroup.graphql.client*

* Future packages

Additional context We currently have a few issues that we have mentioned extracting more logic from graphql-java to write it in a pure Kotlin implementation

• https://github.com/ExpediaGroup/graphql-kotlin/issues/358
• https://github.com/ExpediaGroup/graphql-kotlin/issues/155

[smyrick]

This could be less relevant if we helped the graphql-java team and split up their library: https://github.com/graphql-java/graphql-java/issues/336

[dariuszkuc]

Probably would be good to explicitly mention that you are proposing package change only to graphql-kotlin-schema-generator from com.expediagroup.graphql to com.expediagroup.graphql.generator.

federation and spring-server already have right packages*.

*if we decide to provide support for additional servers, maybe spring-server should use package com.expediagroup.graphql.server.x where x is spring/ktor, etc