Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: new GraalVM reflect metadata generator #1739

Merged
merged 2 commits into from
Apr 10, 2023

Conversation

dariuszkuc
Copy link
Collaborator

📝 Description

Creates new graphql-kotlin-graalvm-metadata-generator project that will be used by Gradle and Maven plugins to auto-generate GraalVM reachability metadata. In order to keep the size of PRs manageable, plugin PRs will be created separately.

GraalVM reachability metadata is required by GraalVM to support reflections and resource handling. This feature will be used by plugins as way to simplify running graphql-kotlin servers as GraalVM native images. Without this functionality, end users have to start their applications with GraalVM agent and then manually run ALL possible execution paths (i.e. queries, loading graphiql, etc).

🔗 Related Issues

Creates new `graphql-kotlin-graalvm-metadata-generator` project that will be used by Gradle and Maven plugins to auto-generate GraalVM reachability metadata. In order to keep the size of PRs manageable, plugin PRs will be created separately.

[GraalVM reachability metadata](https://www.graalvm.org/22.2/reference-manual/native-image/metadata/) is required by GraalVM to support reflections and resource handling. This feature will be used by plugins as way to simplify running `graphql-kotlin` servers as GraalVM native images. Without this functionality, end users have to start their applications with GraalVM agent and then manually run **ALL** possible execution paths (i.e. queries, loading graphiql, etc).
@dariuszkuc dariuszkuc added the changes: minor Changes require a minor version label Apr 6, 2023
@@ -53,6 +54,7 @@ project(":graphql-kotlin-client-generator").projectDir = file("plugins/client/gr
project(":graphql-kotlin-sdl-generator").projectDir = file("plugins/schema/graphql-kotlin-sdl-generator")
project(":graphql-kotlin-hooks-provider").projectDir = file("plugins/schema/graphql-kotlin-hooks-provider")
project(":graphql-kotlin-federated-hooks-provider").projectDir = file("plugins/schema/graphql-kotlin-federated-hooks-provider")
project(":graphql-kotlin-graalvm-metadata-generator").projectDir = file("plugins/server/graphql-kotlin-graalvm-metadata-generator")
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re: new server directory - this logic didn't make much sense to put under existing schema directory, directory is just used for grouping related modules

maybe we should move schema projects under server functionality? or just keep those separate

@dariuszkuc dariuszkuc added the module: plugin Issue affects the plugins code label Apr 6, 2023
@samuelAndalon samuelAndalon merged commit 403603c into ExpediaGroup:master Apr 10, 2023
@dariuszkuc dariuszkuc deleted the graalvm_metadata branch May 19, 2023 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes: minor Changes require a minor version module: plugin Issue affects the plugins code
Development

Successfully merging this pull request may close these issues.

None yet

2 participants