-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[TablePagination] Re-introduce deprecated onChangePage
to ActionsComponent
#27407
Conversation
Details of bundle changes.Comparing: 4fe0df5...4a7bc07 Details of page changes
|
1328d7e
to
416742a
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.
I believe we need to adjust the typings
onChangePage: onChangePageProp, | ||
onPageChange: onPageChangeProp, | ||
onChangePage, | ||
onPageChange, |
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.
We should make this optional prop too, no? https://github.com/mui-org/material-ui/blob/416742a8fddf03cffba2a68c90b63662bfb5f814/packages/material-ui/src/TablePagination/TablePagination.d.ts#L35
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.
Why is this relevant to prop destructuring?
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.
What I meant is that, in order to fix the issue, we need to make both props optional in this component too, as we made them in TablePaginationActions
. Currently onPageChange
is required.
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.
What I meant is that, in order to fix the issue
What issue are you referring to? The original issue is fixed and the test suite is green. You're probably not talking about the runtime which is confusing since the conversation is targetted at the .js file.
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.
@mnajdova I would personally keep the types failing, to give a stronger signal to developers that they need to update their code. But no strong point of view.
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.
Agree the runtime issue is fixed, I thought that it's good chance to fix the changed interface as well, as it is a breaking change for the typescript users. Here is the discussion around it: #23789 (comment)
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 don't understand how the types are failing. I only have the issue and test suite to go off. If you think there's a problem, please provide a concrete example.
…s.d.ts Co-authored-by: Marija Najdova <mnajdova@gmail.com>
Can't make this truyl type safe since either function has to be declared not both. And what is require depends on the contextual TablePagination usage. Let's just ensure runtime and compile time don't complain about the common use cases.
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
Awesome, thanks for the fix! Do you have any idea of when this bug fix will be released? The react-admin users keep on reporting the underlying bug, so it seems to be very annoying. |
onChangePage
to ActionsComponent
onChangePage
to ActionsComponent
Closes #27192
Verified: https://codesandbox.io/s/awesome-frost-5nxj0