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
I have module ::schema
I have module data-user::net which depends on ::schema
data-user::net is abstraction module and only declared graphql fragments
I have data-user::net::impl
data-user::net::impl declared queries and mutations
it depends on ::schema & data-user::net
But without apolloMetadata queries are not generated properly
basically
in both ::net and net:impl modules I was applyin groovy convention plugin
plugins {
id 'com.apollographql.apollo3'
}
apollo {
service("service") {
packageName.set("network.schema")
useSchemaPackageNameForFragments.set(true)
generateApolloMetadata.set(true)
}
}
dependencies {
apolloMetadata projects.networkSchema
api projects.networkSchema
}
This approach does not work in Apollo 4. I do not know how to achieve the same behavior.
Basically in Apollo 3 it was as if extending schema and adding dependant modules data, which is no longer the case in Apollo 4 (unless I miss something)
Describe the solution you'd like
Provide mechanism similar to apollo metadata or revert usage of apolloMetadata or provide ability to add multiple dependencies (dependsOn) so each downstream module can add on top of current (eg. fragment/queries/etc)
The text was updated successfully, but these errors were encountered:
Use case
apolloMetadata is no longer supported in Apollo 4
Before migration to 4 i was using apolloMetadata
I have module ::schema
I have module data-user::net which depends on ::schema
data-user::net is abstraction module and only declared graphql fragments
I have data-user::net::impl
data-user::net::impl declared queries and mutations
it depends on ::schema & data-user::net
But without apolloMetadata queries are not generated properly
basically
in both ::net and net:impl modules I was applyin groovy convention plugin
and additionally in net:impl module
apolloMetadata data-user::net
implementation data-user::net
This approach does not work in Apollo 4. I do not know how to achieve the same behavior.
Basically in Apollo 3 it was as if extending schema and adding dependant modules data, which is no longer the case in Apollo 4 (unless I miss something)
Describe the solution you'd like
Provide mechanism similar to apollo metadata or revert usage of apolloMetadata or provide ability to add multiple dependencies (dependsOn) so each downstream module can add on top of current (eg. fragment/queries/etc)
The text was updated successfully, but these errors were encountered: