mirror of
https://github.com/zulip/zulip.git
synced 2025-11-04 05:53:43 +00:00
40b1f6eb4e
Fixes #20028. There's no reason to have a special `RealmCreationKey` class - the `Confirmation` system already does this job. This is somewhat complicated by the need to write a migration for `RealmCreationKey`->`Confirmation` for pre-existing, valid objects, to avoid breaking realm creation links that haven't been used yet.
28 lines
856 B
Python
28 lines
856 B
Python
# Generated by Django 5.2.3 on 2025-07-04 19:08
|
|
|
|
import django.utils.timezone
|
|
from django.db import migrations, models
|
|
|
|
|
|
class Migration(migrations.Migration):
|
|
dependencies = [
|
|
("zerver", "0746_alter_channelfolder_unique_together_and_more"),
|
|
]
|
|
|
|
operations = [
|
|
migrations.CreateModel(
|
|
name="RealmCreationStatus",
|
|
fields=[
|
|
(
|
|
"id",
|
|
models.BigAutoField(
|
|
auto_created=True, primary_key=True, serialize=False, verbose_name="ID"
|
|
),
|
|
),
|
|
("status", models.IntegerField(default=0)),
|
|
("date_created", models.DateTimeField(default=django.utils.timezone.now)),
|
|
("presume_email_valid", models.BooleanField(default=False)),
|
|
],
|
|
),
|
|
]
|