We're currently running into <this issue> in our r...
# general
a
We're currently running into this issue in our repo. I suppose we could just disable that rule, but I was wondering if anyone here knew of a work around, or if anyone knows if any fixes for it are in the works?
h
I think as a workaround you can play around with the batch sizes so that everything ends up in a single batch?
But really this is a bug, if a linter cares about structure then the partitioning should handle that for you.
a
I ended up just disabling the rule since it wasn't that crucial to have.