@remit/backend 0.0.11 → 0.0.12

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remit/backend",
-  "version": "0.0.11",
+  "version": "0.0.12",
   "description": "Remit Mail Inspector API backend",
   "license": "MIT",
   "author": "",

package/src/handlers/thread.test.ts

@@ -18,15 +18,18 @@ const row = (
 ): Row => ({ threadMessageId, messageIdHeader, createdAt });
 
 describe("buildListThreadMessagesOptions", () => {
-	it("defaults to newest-first and hides soft-deleted messages", () => {
+	it("defaults to oldest-first and hides soft-deleted messages", () => {
 		assert.deepEqual(buildListThreadMessagesOptions({}), {
-			order: "desc",
+			order: "asc",
 			excludeDeleted: true,
 		});
 	});
 
 	it("honours an explicit order", () => {
-		assert.equal(buildListThreadMessagesOptions({ order: "asc" }).order, "asc");
+		assert.equal(
+			buildListThreadMessagesOptions({ order: "desc" }).order,
+			"desc",
+		);
 	});
 
 	it("carries no mailbox filter, so sent messages stay in the conversation", () => {

package/src/handlers/thread.ts

@@ -251,11 +251,16 @@ export const executeThreadSearch = async (
  * A conversation is never scoped to one mailbox: the user's own replies live
  * in Sent, filed messages live in their folder, and all of them belong to the
  * same thread (#46).
+ *
+ * The default order is `asc`: a conversation is read in the order it happened,
+ * so a reply follows the message it answers (#81). The ordering is the query's,
+ * not the handler's — `listByThread` sorts on sentDate with `threadMessageId`
+ * breaking ties, so it holds across pages rather than within one response.
  */
 export const buildListThreadMessagesOptions = (query: {
 	order?: "asc" | "desc";
 }) => ({
-	order: query.order ?? ("desc" as const),
+	order: query.order ?? ("asc" as const),
 	excludeDeleted: true,
 });