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

fix: consistent forms for UI #8922

Merged
merged 3 commits into from
Apr 4, 2022
Merged

Conversation

saumeya
Copy link
Contributor

@saumeya saumeya commented Mar 29, 2022

closes #5443 #5262

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Before
https://user-images.githubusercontent.com/17771352/160873344-3ada56ad-3026-41e5-ba26-0eb82b84e36f.mp4

After

online-screen-recorder-2022-03-31--18-09-39.mp4

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • Optional. My organization is added to USERS.md.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).

Signed-off-by: saumeya <saumeyakatyal@gmail.com>
@saumeya saumeya requested review from ciiay, rbreeze and alexmt March 29, 2022 11:35
@codecov
Copy link

codecov bot commented Mar 29, 2022

Codecov Report

Merging #8922 (16fa5e9) into master (a5933db) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8922      +/-   ##
==========================================
- Coverage   45.00%   44.95%   -0.05%     
==========================================
  Files         212      212              
  Lines       25272    25272              
==========================================
- Hits        11373    11362      -11     
- Misses      12292    12306      +14     
+ Partials     1607     1604       -3     
Impacted Files Coverage Δ
applicationset/services/scm_provider/github.go 63.52% <0.00%> (-17.65%) ⬇️
util/settings/settings.go 48.10% <0.00%> (ø)
applicationset/services/scm_provider/utils.go 88.50% <0.00%> (+4.59%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a5933db...16fa5e9. Read the comment docs.

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to provide a screenshot of the change.

Copy link
Contributor

@ciiay ciiay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a big task and you did a great job! It looks much better now. I only have two things I want to mention, and you may don't have to finish it within this scope.

1, How about for required fields, can we add “*” to the label as an indicator? It’s just an easier way to apply across the app. E.g. Repo URL is required. 
On project details page, there are a few “*”s, what does it mean there? If it means required as well, we can make it consistent across the app.
2, Warning message doesn’t match the label name. E.g. “Name” v.s. “Project name is required”, “Repository URL” v.s. “Repo URL is required”, “Repository Server Name” v.s. “Repository server name is required”

@saumeya
Copy link
Contributor Author

saumeya commented Mar 31, 2022

It's a big task and you did a great job! It looks much better now. I only have two things I want to mention, and you may don't have to finish it within this scope.

1, How about for required fields, can we add “” to the label as an indicator? It’s just an easier way to apply across the app. E.g. Repo URL is required. 
On project details page, there are a few “”s, what does it mean there? If it means required as well, we can make it consistent across the app. 2, Warning message doesn’t match the label name. E.g. “Name” v.s. “Project name is required”, “Repository URL” v.s. “Repo URL is required”, “Repository Server Name” v.s. “Repository server name is required”

Thanks Yi, I definitely noticed these, but wasn't sure - as this would involve a lot more changes. Let me sync up with you today and we could go over these points quickly.

Signed-off-by: saumeya <saumeyakatyal@gmail.com>
@saumeya saumeya requested review from ciiay and terrytangyuan March 31, 2022 18:13
Copy link
Contributor

@reginapizza reginapizza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey Saumeya! Tested it out and it looks great, thanks :)

Copy link
Contributor

@ciiay ciiay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Thanks for the update! Looks great 👍

Copy link
Member

@terrytangyuan terrytangyuan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking great!

@rbreeze rbreeze enabled auto-merge (squash) April 4, 2022 22:03
Copy link
Collaborator

@alexmt alexmt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you for cleaning up UI!

@rbreeze rbreeze merged commit e53a3f8 into argoproj:master Apr 4, 2022
ashutosh16 pushed a commit to ashutosh16/argo-cd that referenced this pull request Apr 9, 2022
Signed-off-by: saumeya <saumeyakatyal@gmail.com>
Co-authored-by: Remington Breeze <remington@breeze.software>
Signed-off-by: asingh51 <Ashutosh_Singh@intuit.com>
wojtekidd pushed a commit to wojtekidd/argo-cd that referenced this pull request Apr 25, 2022
Signed-off-by: saumeya <saumeyakatyal@gmail.com>
Co-authored-by: Remington Breeze <remington@breeze.software>
Signed-off-by: wojtekidd <wojtek.cichon@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove colons from summary view
6 participants