codeant-ai-for-open-source[bot] commented on code in PR #40525:
URL: https://github.com/apache/superset/pull/40525#discussion_r3325195020
##########
superset-frontend/src/features/alerts/AlertReportModal.tsx:
##########
@@ -1397,12 +1422,24 @@ const AlertReportModal:
FunctionComponent<AlertReportModalProps> = ({
}
};
+ const openDashboardInNewTab = (dashboardId?: number | string | null) => {
+ if (!dashboardId) return;
+ const url = `/superset/dashboard/${dashboardId}`;
+ window.open(url, '_blank', 'noopener');
+ };
+
const onChartChange = (chart: SelectValue) => {
getChartVisualizationType(chart);
updateAlertState('chart', chart || undefined);
updateAlertState('dashboard', null);
};
+ const openChartInNewTab = (chartId?: number | string | null) => {
+ if (!chartId) return;
+ const url = `/explore/?slice_id=${chartId}`;
+ window.open(url, '_blank', 'noopener');
+ };
Review Comment:
**🟠Architect Review — HIGH**
The new helpers openDashboardInNewTab/openChartInNewTab build URLs
(`/superset/dashboard/${id}` and `/explore/?slice_id=${id}`) and pass them
directly to window.open without going through ensureAppRoot/navigateTo. In
deployments with a non-empty application_root (subdirectory deployments
validated by pathUtils tests), these URLs will not be prefixed with the app
root, so the "open content in new tab" buttons navigate to incorrect paths and
fail.
**Suggestion:** Use the existing navigation utilities so URLs are run
through ensureAppRoot: e.g., import navigateTo from src/utils/navigationUtils
and call navigateTo(`/dashboard/${dashboardId}`, { newWindow: true }) and
navigateTo(`/explore/?slice_id=${chartId}`, { newWindow: true }) instead of
calling window.open on hardcoded paths.
[Fix in
Cursor](https://app.codeant.ai/fix-in-ide?tool=cursor&prompt_id=f70428d6b1cc4738946af59af81e3545&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=f70428d6b1cc4738946af59af81e3545&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/features/alerts/AlertReportModal.tsx
**Line:** 1425:1441
**Comment:**
*HIGH: The new helpers openDashboardInNewTab/openChartInNewTab build
URLs (`/superset/dashboard/${id}` and `/explore/?slice_id=${id}`) and pass them
directly to window.open without going through ensureAppRoot/navigateTo. In
deployments with a non-empty application_root (subdirectory deployments
validated by pathUtils tests), these URLs will not be prefixed with the app
root, so the "open content in new tab" buttons navigate to incorrect paths and
fail.
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]
