Here is a temporary fix to support Ktor 2.0+ until the project get updated.
I did not get any issues since this change and I hope it will be useful for you.
Step 1:
Import the following file into your Ktor 2.0 project (as KtorPlugin.kt):
Step 2:
Install the above plugin import into your Application as such (Do not use the GraphQL import of the KGraphQL library):
install(GraphQL) {
schema {
mySchema()
}
}
Step 3:
And voila, you should be able to use Ktor 2.0 and the current KGraphQL (0.17.14) into your projects.
I know, it is not an ideal solution but it should keep you going with Ktor updates until the lib get revived.
Future of KGraphQL:
It is unfortunate not having updates for quite a while. Therefore, I suggest anyone to fork this library at least to review and merge any incoming PRs.
To be honest, I haven't found any better alternatives which come close to the simplicity and practicability of this library. I think it would be a waste to terminated this project for lack of support. Until we get further notice from the maintainer, exploring the forking path would not be a bad idea.
Peace
PS: I hope @jeggy & his family are doing all right.
Hey folks,
Here is a temporary fix to support Ktor 2.0+ until the project get updated. I did not get any issues since this change and I hope it will be useful for you.
Step 1: Import the following file into your Ktor 2.0 project (as KtorPlugin.kt):
KtorPlugin.txt
Step 2: Install the above plugin import into your Application as such (Do not use the GraphQL import of the KGraphQL library):
Step 3: And voila, you should be able to use Ktor 2.0 and the current KGraphQL (0.17.14) into your projects. I know, it is not an ideal solution but it should keep you going with Ktor updates until the lib get revived.
Future of KGraphQL:
It is unfortunate not having updates for quite a while. Therefore, I suggest anyone to fork this library at least to review and merge any incoming PRs. To be honest, I haven't found any better alternatives which come close to the simplicity and practicability of this library. I think it would be a waste to terminated this project for lack of support. Until we get further notice from the maintainer, exploring the forking path would not be a bad idea.
Peace
PS: I hope @jeggy & his family are doing all right.