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

31 lines
986 B
Python
Raw Normal View History

models: Enforce stricter requirements on the full_name field. This changes the requirements for UserProfile to disallow some additional characters, with the overall goal of being able to use formataddr in send_mail.py. We don't need to be particularly careful in the database migration, because user full_names are not required to be unique.
2019-06-29 04:41:13 +02:00
# Generated by Django 1.11.20 on 2019-06-28 21:45
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
from unicodedata import category
models: Enforce stricter requirements on the full_name field. This changes the requirements for UserProfile to disallow some additional characters, with the overall goal of being able to use formataddr in send_mail.py. We don't need to be particularly careful in the database migration, because user full_names are not required to be unique.
2019-06-29 04:41:13 +02:00
from django.db import migrations
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
models: Enforce stricter requirements on the full_name field. This changes the requirements for UserProfile to disallow some additional characters, with the overall goal of being able to use formataddr in send_mail.py. We don't need to be particularly careful in the database migration, because user full_names are not required to be unique.
2019-06-29 04:41:13 +02:00
from django.db.migrations.state import StateApps
NAME_INVALID_CHARS = ['*', '`', "\\", '>', '"', '@']
def remove_name_illegal_chars(apps: StateApps, schema_editor: DatabaseSchemaEditor) -> None:
UserProfile = apps.get_model("zerver", "UserProfile")
for user in UserProfile.objects.all():
stripped = []
for char in user.full_name:
if (char not in NAME_INVALID_CHARS) and (category(char)[0] != "C"):
stripped.append(char)
user.full_name = "".join(stripped)
user.save(update_fields=["full_name"])
class Migration(migrations.Migration):
dependencies = [
('zerver', '0235_userprofile_desktop_icon_count_display'),
]
operations = [
python: Use trailing commas consistently. Automatically generated by the following script, based on the output of lint with flake8-comma: import re import sys last_filename = None last_row = None lines = [] for msg in sys.stdin: m = re.match( r"\x1b\[35mflake8 \|\x1b\[0m \x1b\[1;31m(.+):(\d+):(\d+): (\w+)", msg ) if m: filename, row_str, col_str, err = m.groups() row, col = int(row_str), int(col_str) if filename == last_filename: assert last_row != row else: if last_filename is not None: with open(last_filename, "w") as f: f.writelines(lines) with open(filename) as f: lines = f.readlines() last_filename = filename last_row = row line = lines[row - 1] if err in ["C812", "C815"]: lines[row - 1] = line[: col - 1] + "," + line[col - 1 :] elif err in ["C819"]: assert line[col - 2] == "," lines[row - 1] = line[: col - 2] + line[col - 1 :].lstrip(" ") if last_filename is not None: with open(last_filename, "w") as f: f.writelines(lines) Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2020-04-10 05:23:40 +02:00
migrations.RunPython(remove_name_illegal_chars, elidable=True),
models: Enforce stricter requirements on the full_name field. This changes the requirements for UserProfile to disallow some additional characters, with the overall goal of being able to use formataddr in send_mail.py. We don't need to be particularly careful in the database migration, because user full_names are not required to be unique.
2019-06-29 04:41:13 +02:00
]