Prepare for and hold a third pyright/Ruff correction day #8742
Description
As a developer working on IBEX I want to continue to clear out and correct the legacy pyright/ruff errors that are in the system now that we have instigated these checks as standard so that small/urgent changes don't lead to lots of fixing. This will follow on and add to the work started in #8553.
Discussed planning 10/07/25 18:01.72
Acceptance Criteria:
- Identify a day that the majority of the group are free and available and book it in the calendars
- Everyone who can spends as much time as they can on this day fixing these issues
- Open tasks from previous pyright ticket are continued
- The named person on this ticket provides a breakdown of the work needed (including carried over) to facilitate the team undertaking the task (this has to be done before the day is held). Prepare for and hold a second pyright/Ruff correction day [21st May] #8553 can be used as a starting point. The breakdown should make it possible to see at a glance who is working on what and to track PRs and completion of work.
- If required, a follow up ticket for remaining work is created
discussed in planning 12/06/2025 at ~00:27:00
Metadata
Metadata
Assignees
Type
Projects
Status