Spell out the hand-wired ESME's bind, and where a getter-only assignment throws
Mirror / push (push) Has been cancelled
Test / test (18) (pull_request) Successful in 32s
Test / test (20) (pull_request) Successful in 31s
Test / lint (pull_request) Successful in 28s
Test / test (22) (pull_request) Successful in 32s
Test / test (24) (pull_request) Successful in 37s
Test / test (26) (pull_request) Successful in 31s

This commit is contained in:
2026-09-28 04:08:53 +02:00
parent 4bdb1e64b0
commit 2142c2e3bb
3 changed files with 8 additions and 4 deletions
+2 -1
View File
@@ -13,7 +13,8 @@ shape is the same, connect, send, listen for delivery reports, with callbacks re
a `session` event. It no longer calls back once per connection.
- **The id a message is answered with goes to `sendResp({ smsId })`.** `sms.smsId` is read-only: the
id the segments were answered with, the id `sendResp()` was given, or the generated UUID v7.
Assigning to it throws a `TypeError`, since modules are strict mode.
Assigning to it throws a `TypeError` in an ES module or strict-mode script, and is ignored in
sloppy-mode CommonJS.
- **`smsIds` from `sendSms()` is `(string | undefined)[]`**, one entry per segment, positional with
`pduObjs`, `undefined` where the SMSC took the segment without naming an id.
- **`checkuserpass` is `authenticate`**, takes `{ password, session, systemId, systemType }` and