@oxyhq/core 10.1.1 → 10.1.3

package/dist/cjs/session/accountDialogController.js

@@ -30,6 +30,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.AccountDialogController = void 0;
 exports.createAccountDialogController = createAccountDialogController;
 const loggerUtils_1 = require("../utils/loggerUtils");
+const errorUtils_1 = require("../utils/errorUtils");
 const authWebUrl_1 = require("../utils/authWebUrl");
 const oauthPkce_1 = require("../utils/oauthPkce");
 const accountProjection_1 = require("./accountProjection");
@@ -245,10 +246,20 @@ class AccountDialogController {
             graph = await this.oxyServices.listAccounts();
         }
         catch (error) {
-            // A graph-load failure is non-fatal: device rows still render. Surface the
-            // message but keep going with whatever graph we already had.
-            this.error = errorMessage(error);
-            loggerUtils_1.logger.warn('[AccountDialogController] listAccounts failed', { component: 'AccountDialogController' }, error);
+            // A 401 here is the EXPECTED signed-out edge, not a failure: the bearer was
+            // stale/revoked, so `HttpService` already cleared it and emitted
+            // `onTokensChanged(null)`, which drops the graph via `reconcileAuth`. Log at
+            // debug and leave the dialog error-free — a signed-out device with zero
+            // accounts is a normal state, not a warning. Any other error (network, 5xx,
+            // malformed) IS unexpected: surface it and warn while keeping the prior graph
+            // so device rows still render.
+            if ((0, errorUtils_1.extractErrorStatus)(error) === 401) {
+                loggerUtils_1.logger.debug('[AccountDialogController] listAccounts unauthorized (signed out)', { component: 'AccountDialogController' }, error);
+            }
+            else {
+                this.error = errorMessage(error);
+                loggerUtils_1.logger.warn('[AccountDialogController] listAccounts failed', { component: 'AccountDialogController' }, error);
+            }
         }
         if (seq !== this.refreshSeq)
             return; // superseded by a newer refresh
@@ -288,9 +299,16 @@ class AccountDialogController {
             profiles = await this.oxyServices.getUsersByIds(ids);
         }
         catch (error) {
-            // `getUsersByIds` already swallows per-chunk failures and returns `[]`;
-            // this guards the unexpected total failure. Non-fatal — keep prior map.
-            loggerUtils_1.logger.warn('[AccountDialogController] getUsersByIds failed', { component: 'AccountDialogController' }, error);
+            // A 401 is the EXPECTED signed-out edge (stale/cleared bearer) — log at debug.
+            // `getUsersByIds` already swallows per-chunk failures and returns `[]`, so any
+            // OTHER error here is an unexpected total failure worth a warn. Either way keep
+            // the prior profile map.
+            if ((0, errorUtils_1.extractErrorStatus)(error) === 401) {
+                loggerUtils_1.logger.debug('[AccountDialogController] getUsersByIds unauthorized (signed out)', { component: 'AccountDialogController' }, error);
+            }
+            else {
+                loggerUtils_1.logger.warn('[AccountDialogController] getUsersByIds failed', { component: 'AccountDialogController' }, error);
+            }
             return;
         }
         if (seq !== this.refreshSeq)

package/dist/cjs/utils/textNormalization.js

@@ -63,12 +63,11 @@ const INLINE_NEEDS_NORMALIZATION = /[^\x20-\x7E]|^ | $| {2}/;
 /**
  * Same idea as {@link INLINE_NEEDS_NORMALIZATION}, for MULTILINE values: `\n`
  * joins the printable-ASCII fast-path alphabet, and the additional shapes a
- * normalized body can never contain are a space before a line break (trailing
- * horizontal whitespace) and a run of three line breaks (more than one blank
- * line). A single space AFTER a line break is legal — a one-space indent is
- * the author's, and normalization deliberately preserves it.
+ * normalized body can never contain are a space adjacent to a line break — on
+ * either side, since every line is trimmed — and a run of three line breaks
+ * (more than one blank line).
  */
-const MULTILINE_NEEDS_NORMALIZATION = /[^\x20-\x7E\n]|^[ \n]|[ \n]$| {2}| \n|\n{3}/;
+const MULTILINE_NEEDS_NORMALIZATION = /[^\x20-\x7E\n]|^[ \n]|[ \n]$| {2}| \n|\n |\n{3}/;
 /** Any run of whitespace, including tabs, line breaks and Unicode spaces. */
 const ANY_WHITESPACE_RUN = /\s+/g;
 /**
@@ -90,8 +89,18 @@ const LINE_BREAK_FORMS = /\r\n|\r|\p{Zl}|\p{Zp}/gu;
  * Applied AFTER {@link LINE_BREAK_FORMS}, so no line break can hide in it.
  */
 const HORIZONTAL_WHITESPACE_RUN = /[^\S\n]+/g;
-/** Horizontal whitespace at the end of a line — the blank-line spoiler. */
+/**
+ * Horizontal whitespace at the END of a line — the blank-line spoiler: it is
+ * what makes an "empty" line non-empty and hides it from {@link EXCESS_BLANK_LINES}.
+ */
 const TRAILING_HORIZONTAL_WHITESPACE = / +\n/g;
+/**
+ * Horizontal whitespace at the START of a line: source-markup indentation. HTML
+ * collapses it by spec, so it is invisible where the text came from and carries
+ * no meaning — it only becomes visible once a client renders the value with
+ * `white-space: pre-wrap`.
+ */
+const LEADING_HORIZONTAL_WHITESPACE = /\n +/g;
 /** Three or more line breaks: more than one blank line between paragraphs. */
 const EXCESS_BLANK_LINES = /\n{3,}/g;
 /**
@@ -135,20 +144,23 @@ function normalizeInlineText(value) {
  *   2. Unify every line-break form (CRLF, lone CR, U+2028, U+2029) to `\n`.
  *   3. Collapse runs of HORIZONTAL whitespace (spaces, tabs, NBSP and friends)
  *      to a single space. Line breaks are untouched.
- *   4. Strip the horizontal whitespace at the END of each line.
+ *   4. Strip the horizontal whitespace at BOTH ends of every line.
  *   5. Collapse three or more line breaks to exactly one blank line (`\n\n`).
- *   6. Trim both ends.
+ *   6. Trim both ends of the value.
  *
  * STEP 4 MUST PRECEDE STEP 5 — this is the whole point of the function. A
  * "blank" line that actually contains spaces (`"a\n   \n   \nb"`) breaks the
  * run of `\n` characters, so a bare `\n{3,}` collapse (step 5 alone) never sees
  * it and the extra blank lines survive into the UI. That is exactly the bug in
- * federated post bodies. Removing the trailing horizontal whitespace first
- * turns those lines into real, empty lines, which step 5 then collapses.
+ * federated post bodies. Trimming each line first turns those lines into real,
+ * empty lines, which step 5 then collapses.
  *
- * A single space at the START of a line is preserved: only RUNS of horizontal
- * whitespace collapse, and an indent is not trailing whitespace, so a one-space
- * indent is treated as the author's and left alone.
+ * Every line is trimmed on BOTH sides, so a leading indent is removed outright
+ * rather than reduced to one space. Step 3 has already destroyed whatever indent
+ * the author wrote (`"      Mundo"` → `" Mundo"`), so a surviving space would not
+ * be the author's intent — it would be an arbitrary remnant of exactly the
+ * source-markup indentation this function exists to erase, and `pre-wrap` renders
+ * it. Indentation is invisible in HTML by spec; it must be invisible here too.
  *
  * A value that is empty or whitespace-only returns `''`.
  *
@@ -163,6 +175,7 @@ function normalizeMultilineText(value) {
         .replace(LINE_BREAK_FORMS, '\n')
         .replace(HORIZONTAL_WHITESPACE_RUN, ' ')
         .replace(TRAILING_HORIZONTAL_WHITESPACE, '\n')
+        .replace(LEADING_HORIZONTAL_WHITESPACE, '\n')
         .replace(EXCESS_BLANK_LINES, '\n\n')
         .trim();
 }