In the model there's this code for choices this is both in the Queue and Meetings. This results in a new migration whenever get_backend_types() changes. This is dynamic and cannot be predicted
This shouldn't be in the model because it makes it think a migration is missing. Instead we probably should move the choices completely out of the model and into the API.
To test this, you'll have to start up both without Zoom credentials (only in person) and ensure only Zoom appears. Then start with Zoom credentials and insure both In Person and Zoom appears. Also the migrations will need to be run to remove this from the migration process.
In the model there's this code for
choices
this is both in the Queue and Meetings. This results in a new migration wheneverget_backend_types()
changes. This is dynamic and cannot be predictedand
This shouldn't be in the model because it makes it think a migration is missing. Instead we probably should move the choices completely out of the model and into the API.
To test this, you'll have to start up both without Zoom credentials (only in person) and ensure only Zoom appears. Then start with Zoom credentials and insure both In Person and Zoom appears. Also the migrations will need to be run to remove this from the migration process.