-
Notifications
You must be signed in to change notification settings - Fork 101
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(ui-pagination): fix Pagination sometimes displaying non li
elements in lists, fix key errors too
#1839
base: master
Are you sure you want to change the base?
Conversation
…ts in lists, fix key errors too Closes: INSTUI-4422 TEST PLAN: check all examples in inspector, the pagination buttons should all be in lists. There should be no duplicate key warning in the console
@@ -104,7 +104,7 @@ class Pagination extends Component<PaginationProps> { | |||
currentPage: 1, | |||
siblingCount: 1, | |||
boundaryCount: 1, | |||
ellipsis: <li style={{all: 'unset'}}>...</li>, |
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.
I think that this was a bug too, that its a li
should be an internal part of the component. Also they need the `key' prop so React doesnt throw warnings
… | ||
</span> | ||
<li style={{ all: 'unset' }} key="first" aria-hidden="true"> | ||
{this.props.ellipsis} |
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.
now the ellipsis
prop works in the legacy code too
|
Closes: INSTUI-4422
TEST PLAN:
check all examples in inspector, the pagination buttons should all be in lists. There should be no duplicate key warning in the console