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

feat:namespace & release & rollback scrollbar #3936

Closed

Conversation

cookiejoo
Copy link

What's the purpose of this PR

When we use the Apollo configuration, because there are too many configurations, the browser does not appear the drop-down box scroll bar when searching for the configuration. We can only scroll up and down through the mouse scroll axis.

Without a scroll bar, I don't know where the current location is. When I want to select other namespace configurations, I have to keep scrolling the mouse.

This is extremely inconvenient.

So,It is desirable to display a scroll bar and fix the height of each namespace configuration, which greatly facilitates the selection of namespace configuration and the location of the current space configuration.

Which issue(s) this PR fixes:

Fixes #3928

Brief changelog

remove ::-webkit-scrollbar css and fixed div height

Follow this checklist to help us incorporate your contribution quickly and easily:

  • Read the Contributing Guide before making this pull request.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit tests to verify the code.
  • Run mvn clean test to make sure this pull request doesn't break anything.
  • Update the CHANGES log.

@github-actions
Copy link

github-actions bot commented Aug 31, 2021

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@cookiejoo
Copy link
Author

I have read the CLA Document and I hereby sign the CLA

@@ -546,6 +546,12 @@ table th {

::-webkit-scrollbar-thumb:vertical:hover {
background: rgba(255, 255, 255, 0);
}*/

.namespace-view-table-scrollbar {
Copy link
Member

Choose a reason for hiding this comment

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

we already have the Expand/Collapse button for every namespace, is it necessary to limit its height?

Copy link
Author

Choose a reason for hiding this comment

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

Because it is troublesome to display and view the configuration under a lot of configurations.

For example, there is a namespace with a configuration of 1000 or more. When I move up and down, I sometimes scroll to a very deep place, and then go back and find that the shrink button is far away. If the height is fixed at this time, finding the shrink button will greatly reduce my scrolling operation at this time.

Thank you for your time。

Copy link
Member

Choose a reason for hiding this comment

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

Thanks for the feedback. However I don't quite favor the idea to add the scrollbar for configuration items. Wouldn't it be better to add pagination for very long namespaces?

Copy link
Author

Choose a reason for hiding this comment

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

Maybe adding a scrollbar is good for our users,Pagination is also a good idea,
I wonder if your future plan for this page long namespaces is about this optimization?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, pagination is in the to-do list #1261

Copy link
Author

@cookiejoo cookiejoo Sep 4, 2021

Choose a reason for hiding this comment

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

Maybe i can try add pagination in my company ENV,I can do something for community,I can contribute to the community。
Although I'm not a professional UI。

Copy link
Member

Choose a reason for hiding this comment

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

This sounds great!

@nobodyiam
Copy link
Member

BTW, please also update the CHANGES.md.

@nobodyiam
Copy link
Member

@lepdou would you please help to review this pr and #3925? They seems to solve the same issue with different ways.

Copy link
Member

@zouyx zouyx left a comment

Choose a reason for hiding this comment

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

Fix conflicts pls

@codecov-commenter
Copy link

Codecov Report

Merging #3936 (a29e6e4) into master (f909b8d) will decrease coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #3936      +/-   ##
============================================
- Coverage     50.81%   50.77%   -0.05%     
+ Complexity     2468     2466       -2     
============================================
  Files           475      475              
  Lines         14608    14608              
  Branches       1523     1523              
============================================
- Hits           7423     7417       -6     
- Misses         6655     6665      +10     
+ Partials        530      526       -4     
Impacted Files Coverage Δ
...framework/apollo/openapi/entity/ConsumerAudit.java 42.42% <0.00%> (-6.07%) ⬇️
...ework/apollo/internals/RemoteConfigRepository.java 86.25% <0.00%> (-3.13%) ⬇️
...amework/apollo/openapi/util/ConsumerAuditUtil.java 89.18% <0.00%> (-2.71%) ⬇️
...mework/apollo/openapi/service/ConsumerService.java 54.16% <0.00%> (-1.67%) ⬇️
.../apollo/internals/RemoteConfigLongPollService.java 77.10% <0.00%> (-1.21%) ⬇️
...ervice/service/ReleaseMessageServiceWithCache.java 87.05% <0.00%> (+1.17%) ⬆️
.../framework/apollo/spring/property/SpringValue.java 89.47% <0.00%> (+1.75%) ⬆️
...nfigservice/service/AccessKeyServiceWithCache.java 84.69% <0.00%> (+2.04%) ⬆️
...rk/apollo/spring/property/SpringValueRegistry.java 89.18% <0.00%> (+5.40%) ⬆️

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 f909b8d...a29e6e4. Read the comment docs.

@nobodyiam nobodyiam mentioned this pull request Sep 14, 2021
5 tasks
@stale
Copy link

stale bot commented Oct 9, 2021

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 14 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@stale stale bot added the stale label Oct 9, 2021
@stale
Copy link

stale bot commented Oct 23, 2021

This pull request has been automatically closed because it has not had activity in the last 14 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@stale stale bot closed this Oct 23, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Oct 23, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

命名空间配置下拉滚动条修改需求评审
4 participants