-
Notifications
You must be signed in to change notification settings - Fork 356
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
Do not run move of new pagination and remove of old one when new one is present #1556
Conversation
@miq-bot add_label bug |
@skateman this fixes the bug we were talking about, please review and check if it is OK. |
I was testing it and found out a strange behavior. If you remove an element (did with the last one on the last page), the whole paginator breaks and stops working... |
8cf2ad2
to
bcfed18
Compare
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.
bcfed18
to
d87a564
Compare
d87a564
to
30937e3
Compare
@karelhala I think the cc issue is an easy fix . . . I will try this out in the meantime. |
…is present When more than one pagination in angular is present remove left overs
30937e3
to
a362564
Compare
Checked commits karelhala/manageiq-ui-classic@e1fa9be~...a362564 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Fixed --> merging. |
After Merge of c0feb50 there was bug when new pagination was present it was removed if page/sorting has changed. So do not run removing of pagination and moving such pagination if new one is already at correct place.
Fixes #1489