simpler naming, matching better the density of the other items - and avoids snake_case and camelCase confusion :)

This commit is contained in:
B. Petersen
2024-11-17 01:33:07 +01:00
parent 1bc6b1e17e
commit 79993f3011
2 changed files with 2 additions and 2 deletions

View File

@@ -1157,7 +1157,7 @@ uint32_t dc_send_videochat_invitation (dc_context_t* context, uint32_t chat_id);
* @param json program-readable data, this is create in JS land as: * @param json program-readable data, this is create in JS land as:
* - `payload`: any JS object or primitive. * - `payload`: any JS object or primitive.
* - `info`: optional informational message. will be shown in chat an may be added as system notification. * - `info`: optional informational message. will be shown in chat an may be added as system notification.
* - `notifyUsers`: optional array of user `addr` that should be notified eg. by a sound. * - `notify`: optional array of user `addr` that should be notified eg. by a sound.
* note that still all users get the update payload and the `info` message shown in a chat. * note that still all users get the update payload and the `info` message shown in a chat.
* - `document`: optional document name. shown eg. in title bar. * - `document`: optional document name. shown eg. in title bar.
* - `summary`: optional summary. shown beside app icon. * - `summary`: optional summary. shown beside app icon.

View File

@@ -323,7 +323,7 @@ impl Context {
) )
.await?; .await?;
} else { } else {
// TODO: change add_info_msg_with_cmd() to emit DC_EVENT_INCOMING_MSG if update.notifyUsers refers to us // TODO: change add_info_msg_with_cmd() to emit DC_EVENT_INCOMING_MSG if update.notify refers to us
chat::add_info_msg_with_cmd( chat::add_info_msg_with_cmd(
self, self,
instance.chat_id, instance.chat_id,