This is missing from this particular model for no reason. We don't have much use for the UUID now, but it doesn't mean we might not have use in the future. And generally it's consistent to have the UUID for all objects.
Should be done at the same time as #1414 to avoid generating unnecessary migrations.
mikkonie
commented
5 months ago
This is missing from this particular model for no reason. We don't have much use for the UUID now, but it doesn't mean we might not have use in the future. And generally it's consistent to have the UUID for all objects.
Should be done at the same time as #1414 to avoid generating unnecessary migrations.