This is fully supported in the backend and the frontend does not look awful. We just prohibit it when creating new events/categories.
Removing those restrictions and ensuring (especially in the category picker) that a case of a category containing both is properly handled (we may even be able to remove some code there related to restricting things based on what a category contains!) should be enough.
Once we did this, we can finally cache certain things such as category event counts, instead of querying freshly from the DB every single time (ideally in a separate task).
The text was updated successfully, but these errors were encountered:
This is fully supported in the backend and the frontend does not look awful. We just prohibit it when creating new events/categories.
Removing those restrictions and ensuring (especially in the category picker) that a case of a category containing both is properly handled (we may even be able to remove some code there related to restricting things based on what a category contains!) should be enough.
Once we did this, we can finally cache certain things such as category event counts, instead of querying freshly from the DB every single time (ideally in a separate task).
The text was updated successfully, but these errors were encountered: