improve performance of duplicate displayname finding
fix code formatting
move member autocomplete disambiguation to AutocompleteMemberPresenter and preserve original order
Add mxid to autocomplete suggestion if more than one user in a room has the same displayname, closes#1823
Remove the old style Markdown templates and replace with new style yaml
templates. New templates match those used in element-web.
Note that issue labels will been to be renamed to match element-web
before this PR can be merged.
Signed-off-by: Ekaterina Gerasimova <ekaterinag@element.io>
* develop: (34 commits)
version++
Changelog added.
Translated using Weblate (German)
Translated using Weblate (Chinese (Simplified))
Translated using Weblate (German)
Translated using Weblate (Russian)
Translated using Weblate (Russian)
Fix error when sending encrypted message if someone in the room logs out.
Translated using Weblate (Russian)
Translated using Weblate (Russian)
Translated using Weblate (Portuguese (Brazil))
Translated using Weblate (Indonesian)
Translated using Weblate (French)
Translated using Weblate (Indonesian)
Translated using Weblate (Latvian)
Translated using Weblate (Frisian)
Translated using Weblate (Albanian)
add towncrier
Translated using Weblate (Czech)
Translated using Weblate (Chinese (Traditional))
...
Verification flows have something called a transaction id. This is a
client-set custom ID that identifies the flow and is established by the
first message that gets sent out. This transaction ID needs to be kept the
same and be part of all events that are sent during the verification flow.
To-device requests have something called a transaction id. This is a
client-set custom ID that identifies a given request. It is used to
ensure idempotency of requests, i.e. retrying to send a request won't
result in two events being sent as long as the transaction id is kept
the same.
This patch removes usage of the first type of transaction ID for the
second use-case.
This closes: #3589.
