zulip/zerver/migrations/0091_realm_allow_edit_histo...

# Generated by Django 1.11.2 on 2017-07-16 08:57
from django.db import migrations, models


class Migration(migrations.Migration):

    dependencies = [
        ('zerver', '0090_userprofile_high_contrast_mode'),
    ]

    operations = [
        migrations.AddField(
            model_name='realm',
            name='allow_edit_history',
            field=models.BooleanField(default=True),
        ),
    ]
org-permissions: Add allow_edit_history organiztion setting. This new setting controls whether or not users are allowed to see the edit history in a Zulip organization. It controls access through 2 key mechanisms: * For long-ago edited messages, get_messages removes the edit history content from messages it sends to clients. * For newly edited messages, clients are responsible for checking the setting and not saving the edit history data. Since the webapp was the only client displaying it before this change, this just required some changes in message_events.js. Significantly modified by tabbott to fix some logic bugs and add a test. 2017-07-16 11:00:44 +02:00			`# Generated by Django 1.11.2 on 2017-07-16 08:57`
			`from django.db import migrations, models`

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
org-permissions: Add allow_edit_history organiztion setting. This new setting controls whether or not users are allowed to see the edit history in a Zulip organization. It controls access through 2 key mechanisms: * For long-ago edited messages, get_messages removes the edit history content from messages it sends to clients. * For newly edited messages, clients are responsible for checking the setting and not saving the edit history data. Since the webapp was the only client displaying it before this change, this just required some changes in message_events.js. Significantly modified by tabbott to fix some logic bugs and add a test. 2017-07-16 11:00:44 +02:00			`class Migration(migrations.Migration):`

			`dependencies = [`
			`('zerver', '0090_userprofile_high_contrast_mode'),`
			`]`

			`operations = [`
			`migrations.AddField(`
			`model_name='realm',`
			`name='allow_edit_history',`
			`field=models.BooleanField(default=True),`
			`),`
			`]`