This PR aims to overhaul the way ban/restriction reasons are stored witin the database. Currently, a mixture of two weird systems are used, with a per-user notes field and a ban_reason field within the database. This requires a lot of maintenence work by staff, moving data between the two fields and is hard to interface with programatically.
This system aims to solve this by allowing each ban alongside the info around it to be its own separate entry within the database, including all of the necessary info in one.
This PR aims to overhaul the way ban/restriction reasons are stored witin the database. Currently, a mixture of two weird systems are used, with a per-user notes field and a ban_reason field within the database. This requires a lot of maintenence work by staff, moving data between the two fields and is hard to interface with programatically.
This system aims to solve this by allowing each ban alongside the info around it to be its own separate entry within the database, including all of the necessary info in one.