Hey, i’m trying to modularise the apollo queries w...

# apollo-kotlin

[gmaciel]

Hey, i’m trying to modularise the apollo queries within a mono-repo but getting duplicated class issue, currently this the structure i have:

monorepo
  app-a module
    apollo-a module
  app-b module
    apollo-b module

Currently what i get is:
Cause: duplicate Type XXX generated in modules: apollo-b,apollo-a

What i have tried is this:

within app-a:

dependencies {
    implementation(project(":apollo-a"))
    apolloMetadata(project(":apollo-a"))
}

With apollo-a module:

apollo {
    generateApolloMetadata.set(true)
    generateKotlinModels.set(true)
}

Any suggestions on this?

Apollo version: 2.5.9

[gmaciel]

On top of this i also get this error:

java.lang.IllegalStateException: Symbol for kotlin.collections/mutableMapOf|-4813910536206556932[0] is unbound
	at org.jetbrains.kotlin.ir.symbols.impl.IrBindablePublicSymbolBase.getOwner(IrPublicSymbolBase.kt:52)
	at org.jetbrains.kotlin.ir.symbols.impl.IrSimpleFunctionPublicSymbolImpl.getOwner(IrPublicSymbolBase.kt:74)
	at androidx.compose.compiler.plugins.kotlin.lower.LiveLiteralTransformer.visitCall(LiveLiteralTransformer.kt:663)

[bod]

I’m not completely sure, but if you’re not trying to have a shared Apollo module between your 2 apps, would it make sense to generate the code in 2 separate packages (with rootPackageName) to avoid the clash?

[bod]

this can be done in the root config of apollo-a and apollo-b

[gmaciel]

Sorry, deleted my previous question but they are already generated as different packages, however apollo verification tasks fails.

[bod]

oh 🤔

[bod]

I’m guessing the issue is apollo-a and apollo-b are meant to be independent of each other in your case, but are not, and so the check kicks in.

[bod]

they both define a schema, right?

[gmaciel]

yeah, they both have their own schema and one model an enum, is declared on both

[gmaciel]

each module is part of a different app, so they do not relate at all with each other and are in different packages

[gmaciel]

apollo’s check can’t differentiate from different dependency graphs, thus complains about duplication

[bod]

I have the impression that this is not really supported (disclaimer: still a bit new to the project so may be wrong) 😅.

But this sentence here: Multi-modules requires that one and only one module contains a schema.

[gmaciel]

i think my case is a different thing, i have it within a mono repo, so they are different projects and each has it’s own modules.

[bod]

Would it be possible to have one common apollo module with 2 services (for each schema), and then apollo-a and apollo-b depending on it?

[gmaciel]

let me try if that can work

[gmaciel]

Do you know how the declarations would like look like from:

root level gradle config and then from apollo-a and apollo-b modules?

[gmaciel]

i declared on the root level like:

apollo {
    generateKotlinModels.set(true)
    generateApolloMetadata.set(true)

    service("service-a") {
        sourceFolder = "path"
        rootPackageName = "package"
    }

    service("service-b") {
        sourceFolder = "path"
        rootPackageName = "package"
    }
}

And then how would it look on the consumers?

[bod]

I think assuming the module is named root, simply:

apolloMetadata(project(":root"))
implementation(project(":root"))

[bod]

wait do you mean the actual root project? Or did you create a specific module for this?

[gmaciel]

specific module, there’s not one “root”, as i mentioned before, it’s a mono-repo with several apps