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
The new way of declaring separate dependencies for each module is great for extensibility. But leads to a very poorly readable Build.Gradle file, see how my project now has 20 dependencies for Pluto:
Is there a cleaner way of declaring all essential modules, especially for projects with not just 2 but 3 or more build variants?
Or maybe have a dependency that has all modules bundled?
PS: Love Pluto!
The text was updated successfully, but these errors were encountered:
On Tue, Aug 9, 2022, 7:56 PM Prateek Srivastava ***@***.***> wrote:
@ishaangarg <https://github.com/ishaangarg> this is done,
we have published bundle-core with all the core plugins integrated within.
dependencies {
....
debugImplementation 'com.plutolib.plugins:bundle-core:2.0.4'
releaseImplementation 'com.plutolib.plugins:bundle-core-no-op:2.0.4'
....
}
for more info, refer project README.md
—
Reply to this email directly, view it on GitHub
<#167 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOXRE2FI6OE2IV6TKMHHVTVYJTCVANCNFSM55OHBRKQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
The new way of declaring separate dependencies for each module is great for extensibility. But leads to a very poorly readable Build.Gradle file, see how my project now has 20 dependencies for Pluto:
Is there a cleaner way of declaring all essential modules, especially for projects with not just 2 but 3 or more build variants?
Or maybe have a dependency that has all modules bundled?
PS: Love Pluto!
The text was updated successfully, but these errors were encountered: