Refuse a non-finite number where a text field coerces one
Mirror / push (push) Successful in 4s
Test / lint (pull_request) Successful in 21s
Test / test (18) (pull_request) Successful in 36s
Test / test (20) (pull_request) Successful in 30s
Test / test (22) (pull_request) Successful in 30s
Test / test (24) (pull_request) Successful in 29s
Test / test (26) (pull_request) Successful in 30s
Mirror / push (push) Successful in 4s
Test / lint (pull_request) Successful in 21s
Test / test (18) (pull_request) Successful in 36s
Test / test (20) (pull_request) Successful in 30s
Test / test (22) (pull_request) Successful in 30s
Test / test (24) (pull_request) Successful in 29s
Test / test (26) (pull_request) Successful in 30s
This commit is contained in:
@@ -25,6 +25,10 @@
|
||||
will not match the sender it came from. Ids most SMSCs issue are digits or hex and are unaffected.
|
||||
- A `U+0000` inside a C-Octet String — `source_addr`, `message_id`, `system_id` and the rest — is
|
||||
refused. An Octet String carries a NULL as before.
|
||||
- A number with no decimal spelling — `NaN`, `Infinity`, `-Infinity` — is refused where a text field
|
||||
takes one. `sendSms({ from: NaN })` put the literal sender `NaN` on the wire and reported the send
|
||||
as successful; `message_id`, `source_addr` and every other text field took such a number the same
|
||||
way. A finite number still writes its decimals, so `message_id: 123` is unchanged.
|
||||
|
||||
## 0.5.0
|
||||
|
||||
|
||||
Reference in New Issue
Block a user