From d15e1d56c417c263f4ae15747cb0913070528fb4 Mon Sep 17 00:00:00 2001
From: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
Date: Thu, 13 Aug 2026 18:28:43 -0300
Subject: [PATCH] chore(lint): disable
 @next/next/no-location-assign-relative-destination pending per-case review
 (#10292)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The eslint-config-next bump in #10043 shipped this new rule, flagging 6
pre-existing window.location.href navigations — several are deliberate
full-page reloads (login/logout state reset). Off with tracking issue
rather than a blanket router.push rewrite.
---
 eslint.config.mjs | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/eslint.config.mjs b/eslint.config.mjs
index 1a447da98d..4d54c7e91a 100644
--- a/eslint.config.mjs
+++ b/eslint.config.mjs
@@ -62,6 +62,10 @@ const eslintConfig = [
       "no-implied-eval": "error",
       "no-new-func": "error",
       "no-restricted-imports": ["error", IMPORT_BOUNDARY_RESTRICTIONS],
+      // New rule shipped by the eslint-config-next bump (#10043); flags 6 pre-existing
+      // window.location.href navigations, several of which are deliberate full-page
+      // reloads (login/logout state reset). Off pending per-case review — issue #10292.
+      "@next/next/no-location-assign-relative-destination": "off",
     },
   },
   // G14: DB internals may use the compatibility barrel while it is decomposed; all