Prepare for and hold a second pyright/Ruff correction day [21st May] #8553
Description
Issue 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 #8527.
Acceptance Criteria
What is the acceptance criteria of this ticket? What should the reviewer expect to be complete?
- 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 pyright/Ruff correction day (suggested date 17th October 2024) #8527 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 (Prepare for and hold a third pyright/Ruff correction day #8742 )
How to Review
Before making a PR...
- Provide verbose instructions for the reviewer to test that your changes work and fix the issue
- Describe if/how you have implemented testing for this issue
- Provide screenshots of the feature to help the reviewer if relevant
planning 69:00 2024/10/31
Time in recording of planning meeting: 00h12m 2024/11/28
Discussed planning 05/02/2025 00:30:30