@remit/data-ports 0.0.61 → 0.0.63

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/data-ports",
-  "version": "0.0.61",
+  "version": "0.0.63",
   "type": "module",
   "main": "src/index.ts",
   "types": "src/index.ts",

package/src/message-settlement.ts

@@ -33,13 +33,12 @@ export type MessageSettlementFields = Pick<
  * those handlers `status` stays at its in-flight value (`moving`, `deleting`),
  * which is what separates them from the pair above.
  *
- * Three give-ups this cannot see, and must not pretend to:
+ * Two give-ups this cannot see, and must not pretend to:
  *
- * - A MOVE that gave up leaves `moving` + `failed`, the same pair a first
- *   dropped connection writes. Nothing persisted tells the two apart.
- * - A DELETE that exhausted its retries settles `active` + `synced` (#1143's
- *   `resolveExhaustedMessageDeleteFailure` repairs the row to where the message
- *   actually is), so it reads as fully settled here.
+ * - A MOVE or a DELETE that exhausted its retries settles `active` + `synced`
+ *   (`resolveExhaustedMessageMoveFailure` and
+ *   `resolveExhaustedMessageDeleteFailure` repair the row to where the message
+ *   actually is — #1098, #1005), so both read as fully settled here.
  * - `flag-push` and `placement-move-push` never write either field at all.
  *   Their give-up state lives on their own marker rows.
  */

package/src/types.ts

@@ -385,6 +385,7 @@ export type CreateMessageInput = Omit<
 	| "status"
 	| "syncStatus"
 	| "category"
+	| "classificationState"
 	| "authenticityVerdict"
 	| "hasListUnsubscribe"
 	| "movedByRemit"
@@ -393,6 +394,7 @@ export type CreateMessageInput = Omit<
 	status?: MessageItem["status"];
 	syncStatus?: MessageItem["syncStatus"];
 	category?: MessageItem["category"];
+	classificationState?: MessageItem["classificationState"];
 	authenticityVerdict?: MessageItem["authenticityVerdict"];
 	hasListUnsubscribe?: MessageItem["hasListUnsubscribe"];
 	movedByRemit?: MessageItem["movedByRemit"];
@@ -497,8 +499,10 @@ export type SearchOptions = {
 	 * Any-of set over the denormalized `category` column on the ThreadMessage
 	 * row. An empty or absent set means no category filter. `uncategorized` is
 	 * a member like any other — the column is NOT NULL with that default, so it
-	 * names the not-yet-classified state rather than standing for absence
-	 * (issue #45).
+	 * names "no category" rather than standing for absence (issue #45). It
+	 * matches mail the classifier has not reached and mail it declined to
+	 * categorize alike; `Message.classificationState` is what separates those,
+	 * and no read path filters on it (issue #331).
 	 */
 	category?: ThreadMessageItem["category"][];
 };