mirror of
https://github.com/zulip/zulip.git
synced 2025-11-04 14:03:30 +00:00
c4d8f501d6
This will make more sense as I get deeper into modernizing how we accept narrows from users via the API and represent the narrows in event queues.
37 lines
1.1 KiB
Python
37 lines
1.1 KiB
Python
"""
|
|
This module partly exists to prevent circular dependencies.
|
|
|
|
It also isolates some fairly yucky code related to the fact
|
|
that we have to support two formats of narrow specifications
|
|
from users:
|
|
|
|
legacy:
|
|
[["stream", "devel"], ["is", mentioned"]
|
|
|
|
modern:
|
|
[
|
|
{"operator": "stream", "operand": "devel", "negated": "false"},
|
|
{"operator": "is", "operand": "mentioned", "negated": "false"},
|
|
]
|
|
|
|
And then on top of that, we want to represent narrow
|
|
specification internally as dataclasses.
|
|
"""
|
|
from dataclasses import dataclass
|
|
from typing import Collection, Sequence
|
|
|
|
|
|
@dataclass
|
|
class NarrowTerm:
|
|
# In our current use case we don't yet handle negated narrow terms.
|
|
operator: str
|
|
operand: str
|
|
|
|
|
|
def narrow_dataclasses_from_tuples(tups: Collection[Sequence[str]]) -> Collection[NarrowTerm]:
|
|
"""
|
|
This method assumes that the callers are in our event-handling codepath, and
|
|
therefore as of summer 2023, they do not yet support the "negated" flag.
|
|
"""
|
|
return [NarrowTerm(operator=tup[0], operand=tup[1]) for tup in tups]
|