element-hq / element-hq/element-meta

Keywords aren't sorted

Open
#531 1 comment 0 reactions 0 assignees View on GitHub
A-Notifications A-User-Settings good first issue O-Uncommon T-Enhancement Z-GetYourUpdates
Dominant language
No language data
Stars
112
Forks
26
Avg merge
6h 6m
Merged PRs (30d)
4

Description

### Steps to reproduce

1. I open Settings -> Notifications, click keywords
2. I see my keywords in random order
3. I open another Element instance/profile/whatever with a different account and do the two first steps
4. I see that both accounts have keywords in different order while some keywords are the same.

### Outcome

#### What did you expect?

I expected my keywords to be sorted by some logic that would be same across multiple Matrix accounts, so I could easily see which keywords are missing from which account and add them. (I have a lot of names and my friends keep making me different ones, that I would like to keep keyworded in addition to Mjolnir instance names and similar room specific mod calling words.)

#### What happened instead?

I saw my keywords in two different random orders.

### Operating system

"Fedora release 36 (Thirty Six)"

### Browser information

Microsoft Edge 102.0.1245.39 (Virallinen koontiversio) (64-bittinen)

### URL for webapp

develop.element.io

### Application version

Element-versio: 6d3c49d8664c-react-112b4d149620-js-f0991348e2fa Olm-versio: 3.2.12 ***and*** element desktop flatpak 1.11.1

### Homeserver

pikaviestin.fi is on Synapse 1.64.0 , matrix.org is on Synapse 1.64.0rc2

### Will you send logs?

No

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the Settings → Notifications → keywords view described in the reproduction steps and locate the client code responsible for displaying those entries. Compare the ordering for two accounts, then verify that identical keyword sets use the same deterministic order and that the view still works with differing lists.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.