Assigned
Status Update
No update yet.
Comments
pa...@google.com
ad...@google.com
sh...@google.com
yd...@google.com
je...@google.com
thanks for create this issue instance. It is more related to generated Binding Class in Data Binding is deemed to be Unresolved by KT Editor, when multiple base modules in the project has the same Data Binding classes.
Description
In the spirit of making profiling easier and less prone to errors.
Like Tor Norbye said at the "What's new in Android development tools" session... "make it hard to do the wrong thing"
Currently gradle profiling seems like a bit of magic where I always have to refer to a few blog posts + documentation to get the right bits to test "Hey did bumping up to kotlin 1.9.2 speed up clean builds? Did it affect incremental builds negatively?".
I always take inspiration from this blog post from (the goat) Tony Robalik:https://dev.to/autonomousapps/benchmarking-builds-with-gradle-profiler-oa8 where he asks questions like
"Does the build cache do any good? Let's find out" "testing incremental changes" "I wanted to know what impact [Removing Jetifier would have on build times"