zulip/zulip-terminal

Support autocomplete of wildcard mentions

Offen

#1.489 geöffnet am 23.04.2024

 (3 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Python (352 Forks)github user discovery
area: autocompletefeature parity: 02.1 (or before)feature parity: 08feature parity: 09help wantedhigh prioritymissing feature: user

Repository-Metriken

Stars
 (853 Sterne)
PR-Merge-Metriken
 (Keine gemergten PRs in 30 T)

Beschreibung

Mentions in general are summarized here: https://docs.zulip.com/help/mention-a-user-or-group

Many of the options are autocompleted as documented in our FAQ entry.

Current outstanding elements are:

  • @**topic** (only feature level 224, Zulip 8?)
  • @**stream** / @**all** / @**everyone** (feature level 247 adds channel, will be Zulip 9)

For feature-level-dependence, we should skip autocompleting any that do not match the server version having a sufficiently large feature level. The web app currently only shows the two shortest (available) matching wildcard options - but best to confirm with the web app behavior when implementing.

Implementation of this may depend on elements of #1164, to allow any matching wildcard mentions to be made distinct from stream/group mentions, or other related improvements. In a similar way, we should examine the order of web app autocomplete for comparison.

A connected feature would be to extend notifications, which also relates to some of these elements and could be improved substantially in #666.

This may need some discussion first, but a sample with tests should be well-defined by the above.

Contributor Guide