We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
should be "< 1 2 ... 5 >" not <1 ... 2 ... 5>.
Same at the end: should be "< 1 ... 4 5 >" not "<1 ... 4 ... 5 >"
should be "< 1 2 ... 5 >" not <1 ... 2 ... 5>. should be "< 1 ... 4 5 >" not "<1 ... 4 ... 5 >"
12
No response
created by @baengel
The text was updated successfully, but these errors were encountered:
/cib
Sorry, something went wrong.
Branch fix/issue-706 created!
Create PR for #706
18a3328
🐛 fix(pagination): start and end are not correct (#1013)
7665542
* Create PR for #706 * fix(bal-pagination): set fixed number of pagination buttons * fix(bal-pagination): set fixed number of pagination buttons * chore(): fix tests * chore(): update base images * chore(): trigger build * chore(): fix disabled button background * fix(): set fixed number of pages * chore(): improve pagination * chore(): improve tests * chore(): update base images * chore(): trigger build * fix(bal-pagination): set fixed pagination width * chore(): remove unused screenshots * chore(): set mobile pageRange * chore(): update base images * trigger build --------- Co-authored-by: mladenplaninicic <mladenplaninicic@users.noreply.github.com> Co-authored-by: mladenplaninicic <mladenplaninicic@gmail.com>
mladenplaninicic
Successfully merging a pull request may close this issue.
Current Behavior
should be "< 1 2 ... 5 >" not <1 ... 2 ... 5>.
Same at the end:
should be "< 1 ... 4 5 >" not "<1 ... 4 ... 5 >"
Expected Behavior
should be "< 1 2 ... 5 >" not <1 ... 2 ... 5>.
should be "< 1 ... 4 5 >" not "<1 ... 4 ... 5 >"
Steps to Reproduce
Version
12
Browsers
No response
Device
No response
Code Reproduction URL
No response
Additional Information
created by @baengel
Code of Conduct
The text was updated successfully, but these errors were encountered: