-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Bold in-progress diffs diffrently #7918
Conversation
@iwahbe thanks for chatting with me today!! here's my recommendation: lets leave all colors alone except for the +, -, and status. and because of the accessibility issues here lets use the colors you have for created and deleted (and corresponding +,-), and have creating and deleting (and corresponding +,-) be the same white as the other text in the table. folks will be able to more easily scan the green/white and red/white vs green/light-green and red/light-red. what do you think? |
I think that folks will be more able to scan the green/neutral and red/neutral then the color mix. The problem I have is that except at stack creation and stack destruction, most commands will invoke a combination of create, delete, update and replace CRUD operations, each represented with their own color. My example didn't have that because I'm not playing with a complicated stack. If we implement your suggestion, we will get create visibility into what is in progress vs done, but will loose visibility into what type of operations are in progress. Right now I have it set up to split the difference. The user can choose if they want to see full color (difference between progress and pending within a color), or partial color (only completed operations are colored). @susanev How does that look from your end? |
Diff for pulumi-azuread with merge commit 8685e25 |
Diff for pulumi-random with merge commit 8685e25 |
Diff for pulumi-kubernetes with merge commit 8685e25 |
Diff for pulumi-aws with merge commit 8685e25 |
Diff for pulumi-gcp with merge commit 8685e25 |
Diff for pulumi-azure with merge commit 8685e25 |
lets def decide on one change together. i dont htink this situation calls for allowing folks to pick two different solutions. imma take a closer look at all the colors we are using so we can figure out a way to go with your solution but also not introduce contrast issues. ill get back to ya as soon as i can. |
im not gonna approve cause i havent reviewed the code, but based on the video you sent me im good with this change. thx for doing this work!! |
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.
This looks great @iwahbe ! Just a couple of minor clean-up questions and then should be good to go.
@komalali Thanks for pointing out the convention.
This was a good catch!
Because it made less sense in an earlier commit. I should have restored it. (and now I did) |
I haven't had a chance to try this out. Mind sharing the video, or a screenshot, or https://asciinema.org? |
I'd be happy to. |
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.
LGTM!
Description
This feature makes it easier to see which diffs are in progress vs completed. It does this by bolding the colors of steps that are in progress.
Fixes #7337
Checklist