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 an application with more than 30 flavors, there's some automations I'm doing via flavorizr + local scripts so I can structure it better.
Recently I'm having a lot of trouble solving Git conflicts in the application build.gradle due to the size of these flavors config + our application dependencies.
I think that creating an product-flavors.gradle and applying it on build.gradle would organize it better and make it simpler to do Android changes in the project.
Do you guys have an suggestion of how I can organize it or examples in big projects like mine?
If you think it's plausible I can open a PR with this change
The text was updated successfully, but these errors were encountered:
// ----- BEGIN flavorDimensions (autogenerated by flutter_flavorizr) -----
apply from:'product-flavors.gradle'// ----- END flavorDimensions (autogenerated by flutter_flavorizr) -----
I have an android project tha does it exactly like this. It's far easier to manage and we can separate the Library changes from the application changes
Hello!
I have an application with more than 30 flavors, there's some automations I'm doing via flavorizr + local scripts so I can structure it better.
Recently I'm having a lot of trouble solving Git conflicts in the application
build.gradle
due to the size of these flavors config + our application dependencies.I think that creating an
product-flavors.gradle
and applying it onbuild.gradle
would organize it better and make it simpler to do Android changes in the project.Do you guys have an suggestion of how I can organize it or examples in big projects like mine?
If you think it's plausible I can open a PR with this change
The text was updated successfully, but these errors were encountered: