-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[dashboard] Update design of class settings #11435
Conversation
/werft run 👍 started the job as gitpod-build-fo-settings-classes.2 |
Looking at this now! 👀 |
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.
Thanks for making this change, @Furisto! 🔮
Left a couple of suggestions, nitpicks, and questions below.
Approving to unblock merging but holding to let someone from @gitpod-io/engineering-webapp
take a closer look at the code changes.
/hold
selected={workspaceClass === "g1-standard"} | ||
onClick={() => actuallySetWorkspaceClass("g1-standard")} | ||
category="GENERAL PURPOSE" | ||
friendlyName="Standard" |
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.
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 prefer the current way. The category and the description start with an upper case letter and the class starting with a lower case letter looks out of place to me.
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.
Any option would suffice for now.
Looping in @jldec as this will affect usage page pages which will surface the class.
</svg> | ||
</div> | ||
</SelectableCardSolid> | ||
<WorkspaceClass |
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.
question: Is the SelectableCardSolid
not flexible enough for what we need here? I'd love us to reuse the same component and maintain styles and interaction in one place. Haven't checked in depth but would that require us to update the SelectableCardSolid
component?
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 found it nicer to encapsulate everything that is needed for a workspace class in one place, but I am happy to explore using SelectableCardSolid
instead.
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.
fyi: Opened follow-up issue #11472 to track this.
4cdb19b
to
15141e4
Compare
/unhold |
Description
Update design of class settings
Related Issue(s)
Fixes #11358
How to test
Look at the settings page
Release Notes
Documentation
Werft options: