2023-11-19 19:45:19 +01:00
|
|
|
from datetime import datetime
|
2024-07-12 02:30:25 +02:00
|
|
|
from typing import Annotated, Literal
|
2023-02-03 11:07:35 +01:00
|
|
|
|
|
|
|
from django.http import HttpRequest, HttpResponse
|
|
|
|
from django.utils.timezone import now as timezone_now
|
|
|
|
from django.utils.translation import gettext as _
|
2024-07-04 20:38:59 +02:00
|
|
|
from pydantic import Json, StringConstraints
|
2023-02-03 11:07:35 +01:00
|
|
|
|
2023-02-03 13:21:25 +01:00
|
|
|
from zerver.actions.user_topics import do_set_user_topic_visibility_policy
|
2023-02-03 11:07:35 +01:00
|
|
|
from zerver.lib.response import json_success
|
|
|
|
from zerver.lib.streams import (
|
|
|
|
access_stream_by_id,
|
|
|
|
access_stream_by_name,
|
2023-04-03 09:24:30 +02:00
|
|
|
access_stream_to_remove_visibility_policy_by_id,
|
|
|
|
access_stream_to_remove_visibility_policy_by_name,
|
2023-02-03 11:07:35 +01:00
|
|
|
check_for_exactly_one_stream_arg,
|
|
|
|
)
|
2024-05-11 20:31:44 +02:00
|
|
|
from zerver.lib.typed_endpoint import typed_endpoint
|
2024-07-04 20:38:59 +02:00
|
|
|
from zerver.lib.typed_endpoint_validators import check_int_in_validator
|
2023-02-03 12:57:43 +01:00
|
|
|
from zerver.models import UserProfile, UserTopic
|
2024-01-03 11:51:13 +01:00
|
|
|
from zerver.models.constants import MAX_TOPIC_NAME_LENGTH
|
2023-02-03 11:07:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
def mute_topic(
|
|
|
|
user_profile: UserProfile,
|
2024-07-12 02:30:23 +02:00
|
|
|
stream_id: int | None,
|
|
|
|
stream_name: str | None,
|
2023-02-03 11:07:35 +01:00
|
|
|
topic_name: str,
|
2023-11-19 19:45:19 +01:00
|
|
|
date_muted: datetime,
|
2023-02-03 11:07:35 +01:00
|
|
|
) -> None:
|
|
|
|
if stream_name is not None:
|
|
|
|
(stream, sub) = access_stream_by_name(user_profile, stream_name)
|
|
|
|
else:
|
|
|
|
assert stream_id is not None
|
|
|
|
(stream, sub) = access_stream_by_id(user_profile, stream_id)
|
|
|
|
|
user_topics: Refactor add_topic_mute.
In order to support different types of topic visibility policies,
this renames 'add_topic_mute' to
'set_user_topic_visibility_policy_in_database'
and refactors it to accept a parameter 'visibility_policy'.
Create a corresponding UserTopic row for any visibility policy,
not just muting topics.
When a UserTopic row for (user_profile, stream, topic, recipient_id)
exists already, it updates the row with the new visibility_policy.
In the event of a duplicate request, raises a JsonableError.
i.e., new_visibility_policy == existing_visibility_policy.
There is an increase in the database query count in the message-edit
code path.
Reason:
Earlier, 'add_topic_mute' used 'bulk_create' which either
creates or raises IntegrityError -- 1 query.
Now, 'set_user_topic_visibility_policy' uses get_or_create
-- 2 queries in the case of creating new row.
We can't use the previous approach, because now we have to
handle the case of updating the visibility_policy too.
Also, using bulk_* for a single row is not the correct way.
Co-authored-by: Kartik Srivastava <kaushiksri0908@gmail.com>
Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com>
2022-09-12 16:39:53 +02:00
|
|
|
do_set_user_topic_visibility_policy(
|
|
|
|
user_profile,
|
|
|
|
stream,
|
|
|
|
topic_name,
|
2023-03-12 16:19:42 +01:00
|
|
|
visibility_policy=UserTopic.VisibilityPolicy.MUTED,
|
user_topics: Refactor add_topic_mute.
In order to support different types of topic visibility policies,
this renames 'add_topic_mute' to
'set_user_topic_visibility_policy_in_database'
and refactors it to accept a parameter 'visibility_policy'.
Create a corresponding UserTopic row for any visibility policy,
not just muting topics.
When a UserTopic row for (user_profile, stream, topic, recipient_id)
exists already, it updates the row with the new visibility_policy.
In the event of a duplicate request, raises a JsonableError.
i.e., new_visibility_policy == existing_visibility_policy.
There is an increase in the database query count in the message-edit
code path.
Reason:
Earlier, 'add_topic_mute' used 'bulk_create' which either
creates or raises IntegrityError -- 1 query.
Now, 'set_user_topic_visibility_policy' uses get_or_create
-- 2 queries in the case of creating new row.
We can't use the previous approach, because now we have to
handle the case of updating the visibility_policy too.
Also, using bulk_* for a single row is not the correct way.
Co-authored-by: Kartik Srivastava <kaushiksri0908@gmail.com>
Co-authored-by: Prakhar Pratyush <prakhar841301@gmail.com>
2022-09-12 16:39:53 +02:00
|
|
|
last_updated=date_muted,
|
|
|
|
)
|
2023-02-03 11:07:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
def unmute_topic(
|
|
|
|
user_profile: UserProfile,
|
2024-07-12 02:30:23 +02:00
|
|
|
stream_id: int | None,
|
|
|
|
stream_name: str | None,
|
2023-02-03 11:07:35 +01:00
|
|
|
topic_name: str,
|
|
|
|
) -> None:
|
|
|
|
error = _("Topic is not muted")
|
|
|
|
|
|
|
|
if stream_name is not None:
|
2023-04-03 09:24:30 +02:00
|
|
|
stream = access_stream_to_remove_visibility_policy_by_name(user_profile, stream_name, error)
|
2023-02-03 11:07:35 +01:00
|
|
|
else:
|
|
|
|
assert stream_id is not None
|
2023-04-03 09:24:30 +02:00
|
|
|
stream = access_stream_to_remove_visibility_policy_by_id(user_profile, stream_id, error)
|
2023-02-03 11:07:35 +01:00
|
|
|
|
2023-02-03 13:21:25 +01:00
|
|
|
do_set_user_topic_visibility_policy(
|
2023-03-12 16:19:42 +01:00
|
|
|
user_profile, stream, topic_name, visibility_policy=UserTopic.VisibilityPolicy.INHERIT
|
2023-02-03 13:21:25 +01:00
|
|
|
)
|
2023-02-03 11:07:35 +01:00
|
|
|
|
|
|
|
|
2024-05-11 20:31:44 +02:00
|
|
|
@typed_endpoint
|
2023-02-03 11:07:35 +01:00
|
|
|
def update_muted_topic(
|
|
|
|
request: HttpRequest,
|
|
|
|
user_profile: UserProfile,
|
2024-05-11 20:31:44 +02:00
|
|
|
*,
|
2024-07-12 02:30:23 +02:00
|
|
|
stream_id: Json[int] | None = None,
|
|
|
|
stream: str | None = None,
|
2024-05-11 20:31:44 +02:00
|
|
|
topic: Annotated[str, StringConstraints(max_length=MAX_TOPIC_NAME_LENGTH)],
|
|
|
|
op: Literal["add", "remove"],
|
2023-02-03 11:07:35 +01:00
|
|
|
) -> HttpResponse:
|
|
|
|
check_for_exactly_one_stream_arg(stream_id=stream_id, stream=stream)
|
|
|
|
|
|
|
|
if op == "add":
|
|
|
|
mute_topic(
|
|
|
|
user_profile=user_profile,
|
|
|
|
stream_id=stream_id,
|
|
|
|
stream_name=stream,
|
|
|
|
topic_name=topic,
|
|
|
|
date_muted=timezone_now(),
|
|
|
|
)
|
|
|
|
elif op == "remove":
|
|
|
|
unmute_topic(
|
|
|
|
user_profile=user_profile,
|
|
|
|
stream_id=stream_id,
|
|
|
|
stream_name=stream,
|
|
|
|
topic_name=topic,
|
|
|
|
)
|
|
|
|
return json_success(request)
|
2023-03-31 21:18:12 +02:00
|
|
|
|
|
|
|
|
2024-05-11 20:31:44 +02:00
|
|
|
@typed_endpoint
|
2023-03-31 21:18:12 +02:00
|
|
|
def update_user_topic(
|
|
|
|
request: HttpRequest,
|
|
|
|
user_profile: UserProfile,
|
2024-05-11 20:31:44 +02:00
|
|
|
*,
|
|
|
|
stream_id: Json[int],
|
|
|
|
topic: Annotated[str, StringConstraints(max_length=MAX_TOPIC_NAME_LENGTH)],
|
|
|
|
visibility_policy: Json[
|
2024-07-04 20:38:59 +02:00
|
|
|
Annotated[int, check_int_in_validator(UserTopic.VisibilityPolicy.values)]
|
2024-05-11 20:31:44 +02:00
|
|
|
],
|
2023-03-31 21:18:12 +02:00
|
|
|
) -> HttpResponse:
|
|
|
|
if visibility_policy == UserTopic.VisibilityPolicy.INHERIT:
|
2024-04-16 20:31:49 +02:00
|
|
|
error = _("Invalid channel ID")
|
2023-03-31 21:18:12 +02:00
|
|
|
stream = access_stream_to_remove_visibility_policy_by_id(user_profile, stream_id, error)
|
|
|
|
else:
|
|
|
|
(stream, sub) = access_stream_by_id(user_profile, stream_id)
|
|
|
|
|
|
|
|
do_set_user_topic_visibility_policy(
|
|
|
|
user_profile, stream, topic, visibility_policy=visibility_policy
|
|
|
|
)
|
|
|
|
return json_success(request)
|