-
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
Pagination design fixes #13590
Pagination design fixes #13590
Conversation
annotations in the pull request changed, but user is not allowed to start a job |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.0 |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.1 |
/werft run with-preview with-payment 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.2 |
/werft run with-preview with-payment 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.3 |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.4 |
hi @Hardik500, For us to be able to merge this PR, can you please sign our CLA via this DocuSign form? If there are any questions, you can reach me via [email protected]. |
@meysholdt I've signed the DocuSign |
Thank you for signing the CLA @Hardik500! |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.5 |
started the job as gitpod-build-hardik-pagination-design-fixes.1 because the annotations in the pull request description changed |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.7 |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.8 |
6e50bc7
to
7717c70
Compare
started the job as gitpod-build-hardik-pagination-design-fixes.2 because the annotations in the pull request description changed |
started the job as gitpod-build-hardik-pagination-design-fixes.4 because the annotations in the pull request description changed |
1864607
to
490e4ed
Compare
Hi @Hardik500, sorry for the long delay in reviewing! I hope you don't mind that I rebased your branch so that we don't have to go back and forth too much again. I recorded a short loom. Let me know if you can't view it. |
Hey @laushinka , I am unable to reproduce it. Attaching the video ref below Pagination.For.Workspace.mov |
@Hardik500 Thanks for the recording! That does help. It could be my test cases in my preview environment that's causing it. Could you squash and rebase? |
isDisabled={currentPage === 1} | ||
onClick={prevPage} | ||
label={"Previous"} | ||
arrowReversed={false} |
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.
Instead of calling this arrowReversed
and accepting a boolean, could you keep it as arrowDirection
and accepts a string? This prop is used not only for left and right, but also up and down.
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.
Got it
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.
One question, @laushinka so for "up" and "down" arrowDirection, do I need to handle code for those too in PaginationNavigationButtons
component. Cause right now the code flow would be like this?
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.
You don't have to handle "up" and "down" here because we won't see those in Pagination. The intention is to be consistent with what the <Arrow />
component expects :)
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.
Understood, I have made the respective changes
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.
Thanks! Could you squash and rebase please? :)
c6d715a
to
05244d8
Compare
/werft run with-preview 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.10 |
started the job as gitpod-build-hardik-pagination-design-fixes.8 because the annotations in the pull request description changed |
Rebased and pushed, but job keeps failing. Looping this internally, see relevant discussion (internal). Cc @laushinka |
started the job as gitpod-build-hardik-pagination-design-fixes.10 because the annotations in the pull request description changed |
/werft run with-clean-slate-deployment with-preview 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.11 |
I'm going to approve this to unblock, but holding due to:
/hold |
started the job as gitpod-build-hardik-pagination-design-fixes.16 because the annotations in the pull request description changed |
Looking at this now! 👀 |
/werft run with-clean-slate-deployment with-preview 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.12 |
05244d8
to
12d59f4
Compare
/werft run with-clean-slate-deployment with-preview 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.13 |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.14 |
/werft run 👍 started the job as gitpod-build-hardik-pagination-design-fixes-fork.15 |
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.
Thanks @Hardik500 @laushinka! 🔮
I couldn't test this sufficiently as the preview environment is getting removed always under ~15 minutes, see relevant discussion (internal). Cc @vulkoingim @mads-hartmann
From what I see from the screenshots, this looks good. We can always make minor adjustments later in the styles. ✔️
I hope this is not adding a pagination in the workspaces list as seen in #13590 (comment). From the code changes it seems not but let me know if this is not the case.
Approving and merging.
/unhold |
Thanks @gtsiolis |
Thank you @Hardik500 for the patience and @gtsiolis for the co-reviewing 🙏🏽 |
Description
Changed the design of pagination component to match more with the current theme
Dark Mode:
Light Mode:
Disabled Dark Mode:
Disabled Light Mode:
Hover Dark Mode:
Hover Light Mode:
Related Issue(s)
Fixes #12537, #12027
How to test
Go to any page which has some pagination involved and check the pagination buttons
Release Notes
Documentation
Werft options: