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

[IJ Plugin] Reconsider use Gradle's continuous mode for automatic codegen #5529

Open
BoD opened this issue Jan 12, 2024 · 1 comment
Open

Comments

@BoD
Copy link
Contributor

BoD commented Jan 12, 2024

Currently the automatic codegen feature works by invoking Gradle in continuous mode. While this was a handy way to implement this without having to replicate the file monitoring handled by Gradle, it has the disadvantage of keeping a daemon running always, in BUSY status (not available for other builds) - which consumes memory on the system.

Consider reverting to manually trigger the codegen task when GQL files are touched.

@BoD
Copy link
Contributor Author

BoD commented Jan 12, 2024

Even better if we can bypass Gradle completely and invoke the compiler directly. Work in #5516 should help for this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant