Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(message): fix three stale claims in message module comments

Yudhi Armyndharisab935c95a9c5
diff --git a/src/modules/message/entities/message.entity.ts b/src/modules/message/entities/message.entity.ts
index 53f6f6471..68ca21bed 100644
--- a/src/modules/message/entities/message.entity.ts
+++ b/src/modules/message/entities/message.entity.ts
@@ -4,7 +4,7 @@ import { jsonColumnType } from '../../../common/utils/column-types';
/**
* A `bigint` column reads back as a string on PostgreSQL (pg avoids >2^53 precision loss) but as a
* number on SQLite. WhatsApp epoch-seconds are far below 2^53, so coerce reads to a number for a
- * consistent REST/SDK/MCP contract (entity, DTO, all three SDKs, and dashboard declare `number`).
+ * consistent REST/SDK/MCP contract (entity, DTO, the typed SDKs, and dashboard declare a numeric type).
* Writes pass through unchanged; null stays null.
*/
export const bigintToNumberTransformer: ValueTransformer = {
diff --git a/src/modules/message/message-send.service.ts b/src/modules/message/message-send.service.ts
index 7dfe2b69c..027bd7d24 100644
--- a/src/modules/message/message-send.service.ts
+++ b/src/modules/message/message-send.service.ts
@@ -70,7 +70,7 @@ export interface SaveOutgoingMessageData {
*
* Backpressure is applied at the edges instead: bulk sends self-throttle via
* `delayBetweenMessages` (default 3s) and a per-process concurrent-batch cap (see
- * `BulkMessageService`), and the global throttler enforces per-key rate limits.
+ * `BulkMessageService`), and the global throttler enforces per-route, per-client-IP rate limits.
*/
@Injectable()
export class MessageSendService {
diff --git a/src/modules/message/message-type-backfill.service.ts b/src/modules/message/message-type-backfill.service.ts
index 8b48a3ecf..ec0e2e28f 100644
--- a/src/modules/message/message-type-backfill.service.ts
+++ b/src/modules/message/message-type-backfill.service.ts
@@ -13,9 +13,9 @@ import { createLogger } from '../../common/services/logger.service';
* render wrong (text as a `[chat]` media bubble, voice notes as document links) and stats split the
* same kind across old/new tokens.
*
- * This runs on startup in EVERY DB mode. A TypeORM data migration would NOT suffice: the zero-config
- * SQLite default uses `synchronize: true`, under which `migrationsRun` is false, so migrations never
- * run there. The mapping is forward-only and collision-free (the neutral targets were never valid
+ * This runs on startup in EVERY DB mode. A TypeORM data migration would NOT suffice: a SQLite data DB
+ * under the opt-in DATABASE_SYNCHRONIZE=true (e.g. docker-compose.dev.yml) runs with `migrationsRun`
+ * false, so migrations never run there. The mapping is forward-only and collision-free (the neutral targets were never valid
* raw tokens, and passthrough kinds already match), so re-running on already-converted rows is a
* no-op — safe to execute on every boot.
*/