-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[DataGrid] Make base data source available in the Community plan #16359
base: master
Are you sure you want to change the base?
Conversation
Deploy preview: https://deploy-preview-16359--material-ui-x.netlify.app/ Updated pages: |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
const initialStateWithPagination = React.useMemo( | ||
const initialState = React.useMemo( |
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.
"Pagination" was removed from the name but is still present in the object's value, should it be removed?
paginationModel, | ||
sortModel, | ||
filterModel, | ||
...computeStartEnd(paginationModel), |
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.
It doesn't feel like it needs to be in a separate function.
@@ -26,6 +26,7 @@ import { HeightEntry } from '../../features/rows/gridRowsMetaInterfaces'; | |||
export type GridPipeProcessorGroup = keyof GridPipeProcessingLookup; | |||
|
|||
export interface GridPipeProcessingLookup { | |||
clearDataSourceState: { value: null }; |
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.
Tbh I don't love pipe processors, I feel like they make the flow a bit hard to understand. Is there a way we could use an alternative? Could the newer grid config context be used instead?
Resolves #15373