This fixes federating notes with advanced mfm usage, that looked weird/wrong otherwise.
See also c174f23389
Co-authored-by: syuilo <Syuilotan@yahoo.co.jp>
Changelog: Changed
Turning the MFM render container into a div changes it to display
as a block which messes up rendering in some places, e.g. when
it is used to render user names in "Renoted by".
CSS colors are either 3 or 6 hex digits, not 3 to 6 (which would allow
4 and 5 digit hex codes, which are not accepted).
Also adds an explicit null/undefined check.
Changes the default color for the $[bg ] function to something different
than the fg color so if you use both functions on a piece of text with
default values, the text stays somewhat readable.
The issue was that the detection in the drive component did not see the
contents of `paginationElem.items` because the ref was not properly
exposed. The value of the exposed property was a Proxy of an empty
array that was not a reference to the actual items array. Thus, when
checking if the item already exists or not, it never saw the item and
added it as if new.
closes FoundKeyGang/FoundKey#367
closes FoundKeyGang/FoundKey#368
Changelog: Fixed
These messages are wrong when using the newly added filter and there
are no filtering results. Instead of adding yet another separate
message for an empty pagination, just show the default empty thingy
the pagination component provides already.
The `sort` parameter for /api/drive/show is now more unified with
other endpoints which use +createdAt for sort instead of +created.
closes FoundKeyGang/FoundKey#109
Changelog: Added
The error UUIDs were removed from the backend and trying to match against the IDs
no longer works. This can produce confusing UI behaviour when displaying errors.
closes FoundKeyGang/FoundKey#363
Changelog: Fixed