question re. `generateSourcesDuringGradleSync` bei...

# apollo-kotlin

[Yang]

question re. generateSourcesDuringGradleSync being true by default: does it mean the initial IDE sync time will increase roughly linearly as the number of modules that generate Apollo sources increase?

[Yang]

I assume the IDE sync button can’t take advantage of configuration on demand so it’ll always run it for all modules with the apollo plugin applied?

[bod]

sync time will increase roughly linearly as the number of modules that generate Apollo sources increase

Yes I think that's fair. In our experience the generation time itself is usually not a huge differentiator, it's a fraction of compilation time.

[Yang]

I’m asking because I’m wondering if I should do this for our ksp plugins 😬

[Yang]

The main issue I see is most devs only need the symbols to resolve for their modules in the ide so running it on all modules during sync takes unnecessarily longer

[bod]

I see... yeah I guess maybe you could try it, and if a performance penalty is noticeable, disable it 🙂

[Yang]

so might not be a good idea if you have sandbox app modules for each feature

[bod]

I assume the IDE sync button can’t take advantage of configuration on demand

actually... I've put a ✅ but thinking about it I'm not actually sure of that?

[bod]

what would prevent the IDE from benefitting from it?

[Yang]

The ide wouldn’t know exactly which projects to sync right? So it just syncs all projects defined in settings?

[Yang]

I imagine something like Dropbox focus can help

[bod]

I guess it depends on what "sync" actually does concretely (which I'm not sure) 😅. But I wouldn't be too surprised if config on demand can be benefitted from.

[Yang]

every module would demand to be configured 😄