-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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] Env Variables & Misc Fixes #3581
Conversation
/werft run 👍 started the job as gitpod-build-se-misc-dashboard.6 |
/werft run 👍 started the job as gitpod-build-se-misc-dashboard.7 |
/werft run 👍 started the job as gitpod-build-se-misc-dashboard.9 |
2ef497d
to
68ecbe0
Compare
68ecbe0
to
31742b3
Compare
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.
C'est magnifique! 🌟 Thanks @svenefftinge! Added a few minor comments and one for adding a confirmation modal I didn't include in the initial specs. 🏀
{envVars.length === 0 | ||
? <div className="bg-gray-100 rounded-xl w-full h-96"> | ||
<div className="pt-28 flex flex-col items-center w-96 m-auto"> | ||
<h3 className="text-center pb-3">No Environment Variables</h3> |
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.
issue: Minopr heading color.
<h3 className="text-center pb-3">No Environment Variables</h3> | |
<h3 className="text-center pb-3 text-gray-500">No Environment Variables</h3> |
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.
FWIW The heading color on the empty workspaces list page is not like that. It has a different background though, but I'd argue that a gray background would make it even less attractive to also have a grayish font color?
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.
FWIW The heading color on the empty workspaces list page is not like that.
Yes, we could definitely change that, too. Also, it doesn't have to be too much gray, only a couple of tones lower than the page headings. I'll open a PR for such small fixes today or later.
I'd argue that a gray background would make it even less attractive to also have a grayish font color?
Fair point. No strong feelings on this one.
</div> : null} | ||
<div className="mt-4"> | ||
<h4>Name</h4> | ||
<input className="w-full" type="text" value={ev.name} onChange={(v) => { update({name: v.target.value}) }} /> |
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.
issue: Minor input style issue.
<input className="w-full" type="text" value={ev.name} onChange={(v) => { update({name: v.target.value}) }} /> | |
<input className="w-full border-2 border-gray-400" type="text" value={ev.name} onChange={(v) => { update({name: v.target.value}) }} /> |
</div> | ||
<div className="mt-4"> | ||
<h4>Value</h4> | ||
<input className="w-full" type="text" value={ev.value} onChange={(v) => { update({value: v.target.value}) }} /> |
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.
issue: Minor input style issue.
<input className="w-full" type="text" value={ev.value} onChange={(v) => { update({value: v.target.value}) }} /> | |
<input className="w-full border-2 border-gray-400" type="text" value={ev.value} onChange={(v) => { update({value: v.target.value}) }} /> |
return 'Value must not be empty.'; | ||
} | ||
if (pattern.trim() === '') { | ||
return 'Scope must not be empty.'; |
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.
praise: Loved the kumquat colors here! Will get all validations consistent in the next iteration when auditing colors, and more. 🍊
<button onClick={add} className="font-medium">New Environment Variable</button> | ||
</div> | ||
</div> | ||
: <div> |
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.
issue: Spacing missing.
thought: The amount of semantic inconsistencies (HTML structure) between the same elements and components is slightly increasing!
: <div> | |
: <div class="space-y-2"> |
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've applied the change as suggested but wonder if it is not better to apply space on the childs or at least only on one or the other not on both.
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.
{ | ||
title: 'Delete', | ||
customFontStyle: 'text-red-600 hover:text-red-800', | ||
onClick: () => deleteV(ev) |
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.
filed #3604
It would be good to merger this PR to verify #3569 properly with wildcard repo patterns. |
Will work on the feedback and then merge |
/werft run 👍 started the job as gitpod-build-se-misc-dashboard.13 |
31742b3
to
a024842
Compare
This PR fixes #3400 as well as
the following items from #3507
(https://gitpod.slack.com/archives/C01KGM9BUNS/p1615919354035200).