-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ui] Fix base path when opening a new window #25909
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
@@ -111,12 +113,12 @@ function OpenInLaunchpadButton({ | |||
})), | |||
}), | |||
); | |||
window.open( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may also want to consider linting against this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit 9713613. |
## Summary & Motivation Preserve the base path when opening a new tab for "Open in Launchpad" on a schedule/sensor dry run. I created a hook to wrap extraction of the base path and using `_blank` as the target. I see a few places where we're using `window.open` without applying the base path, so in a followup I'll go through and clean those up too. ## How I Tested These Changes Open a schedule, click "Test schedule", choose a tick. Click "Open in Launchpad", verify that the new tab opens with a URL that includes the base path (deployment) prefix. ## Changelog [ui] Fix "Open in Playground" link when testing a schedule or sensor by ensuring that it opens to the correct deployment.
Summary & Motivation
Preserve the base path when opening a new tab for "Open in Launchpad" on a schedule/sensor dry run.
I created a hook to wrap extraction of the base path and using
_blank
as the target. I see a few places where we're usingwindow.open
without applying the base path, so in a followup I'll go through and clean those up too.How I Tested These Changes
Open a schedule, click "Test schedule", choose a tick. Click "Open in Launchpad", verify that the new tab opens with a URL that includes the base path (deployment) prefix.
Changelog
[ui] Fix "Open in Playground" link when testing a schedule or sensor by ensuring that it opens to the correct deployment.