Skip to content
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: Click on Warehouse in DAG to select view of a specific Freightline #1208

Closed
rbreeze opened this issue Dec 1, 2023 · 2 comments · Fixed by #2028
Closed

UI: Click on Warehouse in DAG to select view of a specific Freightline #1208

rbreeze opened this issue Dec 1, 2023 · 2 comments · Fixed by #2028

Comments

@rbreeze
Copy link
Contributor

rbreeze commented Dec 1, 2023

See comments here: #1156 (reply in thread)

@krancour
Copy link
Member

krancour commented Apr 2, 2024

Related to #1680

I will challenge the idea of "filtered view of Freightline" since that implies Freight from multiple warehouses being present in one single Freightline and I think we're sure we want multiple distinct Freightlines instead.

Clicking a Warehouse to select a Freightline (rather than filter) seems like a reasonable way of implementing a "Freightline picker."

Adding this to v0.6.0.

@krancour krancour modified the milestones: v0.6.0, v0.7.0 May 1, 2024
@krancour krancour changed the title UI: Click on Warehouse in DAG to get filtered view of Freightline UI: Click on Warehouse in DAG to select view of a specific Freightline May 14, 2024
@krancour
Copy link
Member

I think we would also need to change which specific Freightline is shown in response to clicks on Stages as well. Each Stage consumes Freight that originated from a specific Warehouse. When you start a promotion to a specific Stage or to all subscribers of a Stage, I believe we'd need to automatically update which Freightline we show so that it's populated with the relevant Freight for the Stage(s) in question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants