You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of today, we use a separate file to store GraphQL metadata used by the apollo compiler. This means in multi-module scenarios, one typically has to do something like so:
While working, this setup is a bit cumbersome and error prone. It's possible to forget one of the two dependencies.
Instead, we could embed the required GraphQL information in the .jar/.klib file so that the apollo compiler doesn't have to pull an additional artifact.
Describe the solution you'd like
No response
The text was updated successfully, but these errors were encountered:
Use case
As of today, we use a separate file to store GraphQL metadata used by the apollo compiler. This means in multi-module scenarios, one typically has to do something like so:
While working, this setup is a bit cumbersome and error prone. It's possible to forget one of the two dependencies.
Instead, we could embed the required GraphQL information in the
.jar
/.klib
file so that the apollo compiler doesn't have to pull an additional artifact.Describe the solution you'd like
No response
The text was updated successfully, but these errors were encountered: