@remit/data-ports 0.0.62 → 0.0.63

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/message-settlement.ts +5 -6
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@remit/data-ports",
3
- "version": "0.0.62",
3
+ "version": "0.0.63",
4
4
  "type": "module",
5
5
  "main": "src/index.ts",
6
6
  "types": "src/index.ts",
package/src/message-settlement.ts CHANGED
@@ -33,13 +33,12 @@ export type MessageSettlementFields = Pick<
33
33
  * those handlers `status` stays at its in-flight value (`moving`, `deleting`),
34
34
  * which is what separates them from the pair above.
35
35
  *
36
- * Three give-ups this cannot see, and must not pretend to:
36
+ * Two give-ups this cannot see, and must not pretend to:
37
37
  *
38
- * - A MOVE that gave up leaves `moving` + `failed`, the same pair a first
39
- * dropped connection writes. Nothing persisted tells the two apart.
40
- * - A DELETE that exhausted its retries settles `active` + `synced` (#1143's
41
- * `resolveExhaustedMessageDeleteFailure` repairs the row to where the message
42
- * actually is), so it reads as fully settled here.
38
+ * - A MOVE or a DELETE that exhausted its retries settles `active` + `synced`
39
+ * (`resolveExhaustedMessageMoveFailure` and
40
+ * `resolveExhaustedMessageDeleteFailure` repair the row to where the message
41
+ * actually is — #1098, #1005), so both read as fully settled here.
43
42
  * - `flag-push` and `placement-move-push` never write either field at all.
44
43
  * Their give-up state lives on their own marker rows.
45
44
  */