| Age | Commit message (Collapse) | Author |
|---|
|
In the normal case there is always a room that is associated with an
user. So it is in most of the cases, possible to load the metadata
(display name and avatar url) with the help of the room.
In some cases, it is not possible. For example, when opening an user
matrix link pointing to an user and not to a room. In this case, we need
to load the metadata independly of the room, since the user is not
linked to a room.
|
|
Fix broken links in README
|
|
|
|
Add public method to determine if we can change the user password
|
|
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
|
|
|
|
Adds ability remove the avatar
|
|
Not possible previously
|
|
(cherry picked from commit b25785d294669f2bab7dcd1e3cd1fba61991fe46)
|
|
As per the latest iteration of MSC2312, room/, user/ and event/ are
only supported for parsing and replication but not for emitting from
Matrix identifiers.
(cherry picked from commit 86f24d1ecf300b82b3a7253b81a2c392669d2c2b)
|
|
Load user info (display name + avatar) for the local user.
|
|
Co-authored-by: Alexey Rusakov <Kitsune-Ral@users.sf.net>
|
|
|
|
Fix rich edits (transmit)
|
|
Fix rich replies json format (transmit)
|
|
If someone still needs it - fix it; otherwise building with qmake
will be dropped in 0.7
|
|
The new formatted_body was not included into new content on edit
due to badly constructed json.
|
|
With this patch it looks like:
"m.relates_to": {
"m.in_reply_to": {
"event_id": "$another:event.com"
}
}
instead of:
"m.relates_to": {
"event_id": "$another:event.com",
"rel_type": "m.in_reply_to"
},
So it fits the specification by now.
https://matrix.org/docs/spec/client_server/r0.6.1#rich-replies
|
|
|
|
Maybe it's not even that bad, given that an effort is taken to recover
from the internal member list corruption.
|
|
For some reason the installed one doesn't find QtTest dynamic library.
|
|
|
|
Shared libraries are a bit of a chore to handle, maybe another time.
|
|
|
|
That way InstallQuotest feature is also tested. Also fix the Valgrind
suppression file path.
Also: use cmake arguments instead of pushd/popd dance
|
|
|
|
- The feature summary is only generated at the end of the configuration.
- InstallQuotest feature is defined in quotest/CMakeLists.txt now,
and therefore is only available if quotest is getting built
(i.e., if BUILD_TESTING is on).
- API generation configuration code merged from two places into one.
|
|
The current test may fail with "undefined reference" errors discussed at
https://stackoverflow.com/questions/14198972/undefined-symbols-for-qcompare.
|
|
Otherwise CMake's automoc complains that it doesn't see a moc-able class
definition in the file that includes "*.moc".
|
|
Now that CTest is included, quotest target should build (and install)
automatically together with the library.
|
|
It's a missing line from the recent autotests introduction. Without it
CMake doesn't introduce BUILD_TESTING option, and if you explicitly
pass it, fails to configure the project.
|
|
|
|
|
|
This is needed for a few cases like the account list in NeoChat or the
account switcher. In this cases we don't have a room binded to the user
and can't fetch the real display name and avatar.
|
|
|
|
Add more properties to CallCandidateEvent
|
|
|
|
|
|
|
|
Co-authored-by: Kitsune Ral <Kitsune-Ral@users.sf.net>
|
|
|
|
|
|
After going through all the files and the history of commits on them
it was clear that some copyright statements are obsolete (the code has
been overwritten since) and some are missing. This commit tries best to
remedy that, along with adding SPDX tags where they were still not used.
Also, a minimal SPDX convention is documented for further contributions.
Closes #426.
|
|
Enable QT_NO_URL_CAST_FROM_STRING and QT_STRICT_ITERATORS.
|
|
|
|
Port existing copyright statement to reuse using licensedigger
|
|
|
|
|
|
|
|
A new field of std::any type is added that allows clients to "annotate"
any event item with arbitrary kind of data. This is mainly intended so
that clients could calculate certain information about the item (e.g.
special formatting depending on the event contents, or position) without
having to calculate this information every time it is visualised.
In case of Quaternion, the idea is to calculate the "spamminess" of
the event basing on the past activity of a given user in this room -
calculating it upon displaying each event is extremely heavyweight.
|
