Replies: 2 comments
|
Thanks for the report! Yeah, the modular builder is not supposed to have that many inputs. I'm actually not sure what the amount of inputs in the output is referring to though - if it's the amount of files drift ran on, that's not really something under our control.
Just for my interest, how many? Also, how many inputs do you see for |
0 replies
|
With the no modular build we are getting the following output: And with the modular approach: We are also not sure what it means. We are trying to optimize the builds so it doesn't process everything. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have a big Flutter project where we've been using Drift for a long time. Over the years build_runner builds have been taking a bit hit on our CI times. We've been trying to optimize it by using a lower number of transitive imports from the build entry points.
We've noticed that even when lowering this number of imports to a minimum, the Drift modular generation of our code is showing a large number of inputs (1K), and it takes about 30 seconds to analyze.
We are using the latest build_runner 2.5.x, which has many new optimizations in place. When going back to the non modular a low number of inputs shows up. Could this be a bug in the modular generation feature?
All reactions