Wow this is slick and the code looks good to me. I don't know if folks will guess that this interaction exists, so we may need to put a tooltip / meta text somewhere on the page so folks know to use it. (I feel like we need one of those "Loading..." banners with a Top Hat Dagster telling you tricks)

Add tests for Dagit path prefix feature

Need to tie VSCode to Black

Oh wow sorry I didn't catch this when I put this together, I guess this instanceof Array check guarded against a typescript error here... looks great to me 👍

Apply diff feedback

Looks great!

lolo omg that gif

Lock the current pipeline tag into the filter bar on the pipeline runs page

Fix typo, add comments detailing new React hooks

We probably should rename EnvironmentPicker but I can do it later today if that's easier, will require rebuilding the snapshots etc.

Rebase

Looks great let's ship it!

Rename PipelineExecutionButtonGroup > LaunchRootExecutionButton

This looks good to me, I will add on the front-end UI today!

• Fix missing arg forwarding

• Make “starting” state work in re-execute button [temporary fix]

Looks good to me! I think originally we defaulted to "" instead of "*" because on large pipelines we wanted to make you type * explicitly and not try to render that subset immediately. I'm not sure that that is still necessary / an issue.

• Rebase and update tests

Whoops good catch.

Will rebuild snapshots and land this, thanks for the review folks 👍

This looks great to me! Just want to make sure we don't need the run launcher existence check anymore.

• Also apply tooltip to solid column in the logs viewer

Remove the solid subset display from the runs list for now, will revisit in follow-up diff that unifies the presentation across the runs list and run group display.

Looks good - just as a sanity check, the idea is that making the graphQL queries again will always return the latest data from the python files on disk, so to reload dagit you'd just refresh the page in your browser the old-school way?

Hmm will circle back on testing this - I think that we could create a snapshot test that renders an invalid URL and then checks that the post-redirected content is displayed, but something like that is so high level it's likely it'd break and someone would just "update the snapshots" to reflect the broken output. Really needs to be a hand written test I think and we need some more fixtures for those.

• Allow custom (zero-delay) tooltips via a global handler for data-tooltip, with support for custom styling (eg: pipeline sidebar) via data-tooltip-style={}

Looks good!

Looks good to me!

This looks good to me! Nothing blocking just a few minor nits.

This looks good to me! I think PipelineExplorerPath is a good name and I like that it specifically references that it appears in the URL path 👍

This looks awesome and the JS is super clean. Glad you were able to export the RunActionsMenu, etc to share them. let's merge! 👍

Rebase