Closed rjmurillo closed 2 weeks ago
We're pretty close to being able to turn on WarningsAsErrors (which I think is valuable) and these add a whole bunch of new items, some of dubious value (do we really need another compiler warning for TODO, or that
f
isn't a good variable name?)Can we add these and be clean on them at the same time, or suppress violations inline and file TODOs?
I can do two things:
edit: for the second item, new commits will be pushed. For items not cleaned up, they're tracked in #90
If you get done before me you don't need to wait. I think 2 is more important than 1.
Coverage variation | Diff coverage |
---|---|
:white_check_mark: -0.47% (target: -1.00%) | :x: 84.62% (target: 95.00%) |
:rocket: Don’t miss a bit, follow what’s new on Codacy.
Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more
@rjmurillo, this is ready to merge, but the code coverage is blocking merge. Either address, or feel free to lower the threshold for now while we have a lot of churn. I'd be OK with making this informational and not blocking while it's just us.
Several changes: