larvit/smpp-js
3
0
Fork 0
Code Issues Pull Requests Actions Activity

Refuse a TLV input that is no { tagValue }, and the alternate tag names, keep numbers out of octet TLVs, and pin that a TLV is copied off its chunk
Mirror / push (push) Has been cancelled
Details
Test / test (18) (pull_request) Successful in 31s
Details
Test / test (20) (pull_request) Successful in 30s
Details
Test / lint (pull_request) Successful in 22s
Details
Test / test (22) (pull_request) Successful in 39s
Details
Test / test (24) (pull_request) Successful in 31s
Details
Test / test (26) (pull_request) Successful in 32s
Details

Browse Source
This commit is contained in:
Lilleman auf Larv
2026-09-27 15:25:49 +02:00
parent c4b0437323
commit 138464ad0f
5 changed files with 54 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+3 -1
View File
@@ -66,7 +66,9 @@
**A TLV input is keyed by its name, or by its decimal id where the table names none, and `tagId`
is refused.** Write `{ 5142: { tagValue } }` for a vendor tag, not `{ vendor: { tagId: 5142, … } }`.
A name and a `tagId` could disagree, and `{ message_state: { tagId: 5, … } }` went out as tag 5.
A decimal key naming a tag the table knows, `{ 1063: … }`, is refused in favour of the name.
A decimal key naming a tag the table knows, `{ 1063: … }`, is refused in favour of the name, and
so are `alert_on_msg_delivery` and `failed_broadcast_area_identifier` in favour of
`alert_on_message_delivery` and `broadcast_area_identifier`, the names they read back under.
- `cmds.broadcast_sm_resp.tlvMap` is removed; nothing read it.
## 0.5.0