codeant-ai-for-open-source[bot] commented on code in PR #40833:
URL: https://github.com/apache/superset/pull/40833#discussion_r3368065881
##########
superset-frontend/src/utils/navigationUtils.ts:
##########
@@ -30,7 +32,10 @@ export const navigateTo = (
'noopener noreferrer',
);
} else if (options?.assign) {
- window.location.assign(sanitizeUrl(ensureAppRoot(url)));
+ const sanitized = sanitizeUrl(ensureAppRoot(url));
+ if (pendingAssignUrl === sanitized) return;
+ pendingAssignUrl = sanitized;
+ window.location.assign(sanitized);
Review Comment:
**🟠Architect Review — HIGH**
The dedupe latch (pendingAssignUrl) is only ever set and never cleared, so
after a successful navigateTo('/dashboard/new', { assign: true }) the
module-level flag remains set; when the Dashboards or Welcome page is restored
from back-forward cache and the user clicks the same "+ Dashboard"/"+ Chart"
button again, navigateTo sees the same sanitized URL and becomes a no-op,
breaking legitimate repeat create actions.
**Suggestion:** Ensure the guard is not permanent for the entire page
lifetime: either make it time-bounded (e.g., a short double-click window) or
explicitly reset pendingAssignUrl on appropriate lifecycle events (such as
pageshow/popstate) so duplicate-click protection does not block later, valid
navigations.
[Fix in
Cursor](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=57c06d87cb89453099b8ae08910bdec2&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
| [Fix in VSCode
Claude](https://app.codeant.ai/fix-in-ide?tool=vscode-claude&prompt_id=57c06d87cb89453099b8ae08910bdec2&service=github&base_url=https%3A%2F%2Fgithub.com&org=apache&repo=apache%2Fsuperset)
*(Use Cmd/Ctrl + Click for best experience)*
<details>
<summary><b>Prompt for AI Agent 🤖 </b></summary>
```mdx
This is an **Architect / Logical Review** comment left during a code review.
These reviews are first-class, important findings — not optional suggestions.
Do NOT dismiss this as a 'big architectural change' just because the title says
architect review; most of these can be resolved with a small, localized fix
once the intent is understood.
**Path:** superset-frontend/src/utils/navigationUtils.ts
**Line:** 22:38
**Comment:**
*HIGH: The dedupe latch (pendingAssignUrl) is only ever set and never
cleared, so after a successful navigateTo('/dashboard/new', { assign: true })
the module-level flag remains set; when the Dashboards or Welcome page is
restored from back-forward cache and the user clicks the same "+ Dashboard"/"+
Chart" button again, navigateTo sees the same sanitized URL and becomes a
no-op, breaking legitimate repeat create actions.
Validate the correctness of the flagged issue. If correct, How can I resolve
this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative
instruction. If no explicit code suggestion is given, you MUST still draft and
apply your own minimal, localized fix — do not punt back with 'no suggestion
provided, review manually'. Keep the change as small as possible: add a guard
clause, gate on a loading state, reorder an await, wrap in a conditional, etc.
Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask
user if the user wants to fix the rest of the comments as well. if said yes,
then fetch all the comments validate the correctness and implement a minimal fix
```
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
