mirror of
https://github.com/chatmail/core.git
synced 2026-04-17 21:46:35 +03:00
link2xt's review
This commit is contained in:
@@ -407,9 +407,10 @@ char* dc_get_blobdir (const dc_context_t* context);
|
||||
* to not mess up with non-delivery-reports or read-receipts.
|
||||
* 0=no limit (default).
|
||||
* Changes affect future messages only.
|
||||
* - `debug_logging` = Let the core save all events to the database. You should expose this as an advanced
|
||||
* - `debug_logging` = 1=Let the core save all events to the database. You should expose this as an advanced
|
||||
* setting to the user. When they enable it, the core automatically adds a webxdc
|
||||
* message to the device chat where the user can see the log messages.
|
||||
* 0=disable debug logging (default)
|
||||
* - `ui.*` = All keys prefixed by `ui.` can be used by the user-interfaces for system-specific purposes.
|
||||
* The prefix should be followed by the system and maybe subsystem,
|
||||
* e.g. `ui.desktop.foo`, `ui.desktop.linux.bar`, `ui.android.foo`, `ui.dc40.bar`, `ui.bot.simplebot.baz`.
|
||||
|
||||
@@ -468,7 +468,7 @@ impl Context {
|
||||
let webxdc_instance_id = MsgId::new(debug_logging as u32);
|
||||
|
||||
match context
|
||||
.internal_write_status_update(
|
||||
.write_status_update_inner(
|
||||
&webxdc_instance_id,
|
||||
StatusUpdateItem {
|
||||
payload: event.to_json(Some(time)),
|
||||
|
||||
@@ -324,7 +324,7 @@ impl Context {
|
||||
}
|
||||
|
||||
let status_update_serial = self
|
||||
.internal_write_status_update(&instance.id, status_update_item)
|
||||
.write_status_update_inner(&instance.id, status_update_item)
|
||||
.await?;
|
||||
|
||||
let status_update_serial = StatusUpdateSerial(u32::try_from(rowid)?);
|
||||
@@ -339,7 +339,7 @@ impl Context {
|
||||
Ok(status_update_serial)
|
||||
}
|
||||
|
||||
pub(crate) async fn internal_write_status_update(
|
||||
pub(crate) async fn write_status_update_inner(
|
||||
&self,
|
||||
instance_id: &MsgId,
|
||||
status_update_item: StatusUpdateItem,
|
||||
|
||||
Reference in New Issue
Block a user