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: Increase y-margin in resource tree view (#7183) #8597

Merged

Conversation

keithchong
Copy link
Contributor

@keithchong keithchong commented Feb 23, 2022

Signed-off-by: Keith Chong kykchong@redhat.com

This is a follow up issue to the zoom support added via #8290

When the tree structure consists of one long horizontal branch, the floating bar is in the way. In a lot of cases, the floating toolbar is fine to float above the tree contents, because the tree is scrollable. But in this case, the tree structure is not scrollable vertically, so the toolbar is in the way. We should increase the Y-margin.

Problem

Screen Shot 2022-02-23 at 2 22 58 PM

With Fix:

Screen Shot 2022-02-23 at 2 24 33 PM

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.

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).

@codecov
Copy link

codecov bot commented Feb 23, 2022

Codecov Report

Merging #8597 (dd3797b) into master (ebc89ce) will increase coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #8597      +/-   ##
==========================================
+ Coverage   42.57%   42.59%   +0.01%     
==========================================
  Files         177      184       +7     
  Lines       22988    23169     +181     
==========================================
+ Hits         9787     9868      +81     
- Misses      11804    11898      +94     
- Partials     1397     1403       +6     
Impacted Files Coverage Δ
util/helm/client.go 45.14% <0.00%> (-3.37%) ⬇️
reposerver/repository/repository.go 57.39% <0.00%> (-1.27%) ⬇️
server/application/application.go 31.76% <0.00%> (-0.52%) ⬇️
server/repository/repository.go 52.41% <0.00%> (-0.04%) ⬇️
cmd/argocd/commands/app.go 0.52% <0.00%> (-0.02%) ⬇️
util/settings/settings.go 47.91% <0.00%> (ø)
reposerver/repository/lock.go 100.00% <0.00%> (ø)
util/io/paths.go 68.75% <0.00%> (ø)
util/io/componsablefs.go 0.00% <0.00%> (ø)
util/io/closer.go 14.28% <0.00%> (ø)
... and 8 more

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 ebc89ce...dd3797b. Read the comment docs.

@keithchong
Copy link
Contributor Author

/retest

Signed-off-by: Keith Chong <kykchong@redhat.com>
@keithchong keithchong force-pushed the 7183-IncreaseYMarginInResourceTree branch from 4d35f7b to dd3797b Compare March 2, 2022 17:48
@jannfis jannfis merged commit f29151e into argoproj:master Mar 3, 2022
wojtekidd pushed a commit to wojtekidd/argo-cd that referenced this pull request Apr 25, 2022
…j#8597)

Signed-off-by: Keith Chong <kykchong@redhat.com>
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.

3 participants