-
Notifications
You must be signed in to change notification settings - Fork 329
Conversation
803f89c
to
1b932e0
Compare
1b932e0
to
9ea25fc
Compare
9ea25fc
to
3d67458
Compare
3d67458
to
1a295a7
Compare
1a295a7
to
a2dd308
Compare
734dd16
to
c948e21
Compare
2088604
to
191f58e
Compare
91ed551
to
0df236f
Compare
0df236f
to
184003a
Compare
184003a
to
7e22b4d
Compare
7e22b4d
to
a920d41
Compare
@@ -9,7 +9,20 @@ | |||
)}} | |||
<PageHeader @iconName="git-repository"> | |||
<div class="title"> | |||
<h1>{{@model.application.application}}</h1> | |||
<div class="title-wrapper"> |
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.
Not sure I entirely needed to introducing a wrapping element here, but I didn’t want to throw off the title
styling.
One small thought on the "no active workspaces" state. Assuming a user has not created any workspace and is the default space, maybe we should hide the workspace switcher if you only have a single workspace. Seems like it could cause less confusion if you have no knowledge of workspaces. I'm also a little confused by the "no active workspaces" message. In your screenshot, isn't "production" considered an active workspace? Should the message say "No other active workspaces found" to be more clear? @almonk Do you have any thoughts on this? I don't think this change should hold up this PR though, we can change it later if we agree on a different behavior. |
I agree that we shouldn't show the switcher if there's only 1 workspace (and while you can't create them in the UI). @jgwhite what do you think about populating workspace data when the user navigates to an app rather than just in time when the user clicks the dropdown? |
import { module, test } from 'qunit'; | ||
import { Response } from 'miragejs'; | ||
|
||
module('Integration | Component | workspace-switcher', function (hooks) { |
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.
Appreciate how comprehensive these tests are!
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.
Looks good to me! For something so complicated under the hood, this code is super straight forward and clear, great job! 🤠 👍
taskFor(this.loadWorkspaces).perform(); | ||
} | ||
|
||
@task({ restartable: true }) |
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.
I think this is the first time I'm seeing ember-concurrency
and @task
, super interesting
@almonk luckily it already does behave that way, I just artificially slowed things down to make the videos more illustrative. @almonk + @amandakalk I think I’ll go ahead and hide the switcher altogether until we’ve loaded the workspaces and, as you both suggest, only show it under either of these conditions:
|
85b15c5
to
b7d8388
Compare
b7d8388
to
195bed9
Compare
Co-authored-by: Izaak Lauer <[email protected]> Co-authored-by: Alasdair Monk <[email protected]> Co-authored-by: Amanda Cahill <[email protected]>
195bed9
to
9c89ad5
Compare
Why the change?
Addresses #1339
What’s the plan?
What’s not the plan?
Default workspace selection will be addressed in a separate PR. See #2662 for problem statement.
What does it look like?
Switching.Workspace.mp4
Error.Loading.Workspaces.mp4
(note: the loading state no longer appear in the flow above, just the error)
How do I test it?
git checkout ui/workspace-switcher