Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/zerver/migrations/0214_realm_invite_to_stream...

31 lines
1.1 KiB
Python
Raw Normal View History

settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
# Generated by Django 1.11.20 on 2019-04-29 05:29
from django.db import migrations, models
migrations: Use django.db.backends.postgresql.schema. This replaces django.db.backends.postgresql_psycopg2, which has been an alias to django.db.backends.postgresql since Django 1.9.
2020-04-27 07:19:08 +02:00
from django.db.backends.postgresql.schema import DatabaseSchemaEditor
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
from django.db.migrations.state import StateApps
python: Sort migrations/management command imports with isort. This is a preparatory commit for using isort for sorting all of our imports, merging changes to files where we can easily review the changes as something we're happy with. These are also files with relatively little active development, which means we don't expect much merge conflict risk from these changes.
2020-01-14 21:59:46 +01:00
migrations: Refactor the enum type fields. Accessing attributes is the preferred design pattern, as it is more readable.
2020-02-17 17:13:57 +01:00
INVITE_TO_STREAM_POLICY_MEMBERS = 1
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
def handle_waiting_period(apps: StateApps, schema_editor: DatabaseSchemaEditor) -> None:
Realm = apps.get_model('zerver', 'Realm')
migrations: Refactor the enum type fields. Accessing attributes is the preferred design pattern, as it is more readable.
2020-02-17 17:13:57 +01:00
Realm.INVITE_TO_STREAM_POLICY_WAITING_PERIOD = 3
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
Realm.objects.filter(waiting_period_threshold__gt=0).update(
migrations: Refactor the enum type fields. Accessing attributes is the preferred design pattern, as it is more readable.
2020-02-17 17:13:57 +01:00
invite_to_stream_policy=Realm.INVITE_TO_STREAM_POLICY_WAITING_PERIOD)
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
class Migration(migrations.Migration):
dependencies = [
('zerver', '0213_realm_digest_weekday'),
]
operations = [
migrations.AddField(
model_name='realm',
name='invite_to_stream_policy',
migrations: Refactor the enum type fields. Accessing attributes is the preferred design pattern, as it is more readable.
2020-02-17 17:13:57 +01:00
field=models.PositiveSmallIntegerField(default=INVITE_TO_STREAM_POLICY_MEMBERS),
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
),
migrations.RunPython(handle_waiting_period,
migrations: Mark RunPython statements elidable. This will make django automatically remove them when we run squashmigrations. There are still some RunSQL statements which we will have to take care of manually.
2020-04-29 08:43:25 +02:00
reverse_code=migrations.RunPython.noop,
elidable=True),
settings: Create an explicit invite_to_stream_policy setting. This commit creates a new organization setting that determines whether a user can invite other users to streams. Previously this was linked to the waiting period threshold, but this was both not documented and overly limiting. With significant tweaks by tabbott to change the database model to not involve two threshhold fields, edit the tests, etc. This requires follow-up work to make the create stream policy setting work how this code implies it should. Fixes #12042.
2019-04-08 19:23:00 +02:00
]