Closed petermetz closed 1 year ago
@petermetz I want to work on this ticket
Closing due to the linter numbers having gone stale in the meantime. We need to invent a better way of tracking linter warnings for future issues like this that we'll open because the line numbers are ephemeral and therefore not well suited for this.
style: 2021-09-20 linter warnings batch 13 / 26
Description
As of today (20th of September, 2021) we have 260 linter warnings in the codebase. A set of issues were created to fix them in increments of 10 warnings at a time. Each group of 10 linter warnings is a batch. There is a one to one relationship between issues opened on GitHub and batches of 10 linter warnings. The complete list is attached/linked to all the issues, but every given issue should only include fixes to the corresponding batch of warnings to avoid conflicts with others.
For example if an issue has
1 / 26
in it's title, that's batch number one, meaning that the linter warnings that needs to be fixed in the scope of that task are the ones with IDs of 1 to 10, inclusive, as in 1,2,3,4,5,6,7,8,9,10. For2 / 26
in the title, that's batch#2
and the corresponding warnings IDs in the main table are therefore: 11,12,13,14,15,16,17,18,19,20. For3 / 26
in the title, that's batch#3
you get the point...Acceptance Criteria
Full List of Linter Warnings
Important: Do not fix all of these, just a subset of them as per the guidelines in the
Description
section above. Otherwise your pull request might get rejected due to unfixable conflicts.