[material-ui][Table] `slots` and `slotProps` documented properties are not exposed in package

[quibaritaenperdresatrompe]

Steps to reproduce

Link to live example: (required)

Steps:

1. install @mui/material-ui@5.15.10
2. read the TablePagination API documentation for this version and note that slots and slotProps props have a lot of properties e.g. nextButtonIcon
   
3. use the TablePagination component in JSX or override style with theme.components.MuiTablePagination.defaultProps properties
4. note that only actions or select properties are available
   

Current behavior

only actions or select properties are available on slots and slotProps props (on TablePagination component)

Expected behavior

nextButtonIcon or previousButtonIcon properties are available on slots and slotProps props (on TablePagination component) as mentioned in the web documentation

Context

e.g. override theme.components.MuiTablePagination.defaultProps.slots.nextButtonIcon

Your environment

npx @mui/envinfo

    System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 120.0.6099.129
  npmPackages:
    @emotion/react: ^11.11.3 => 11.11.3 
    @emotion/styled: ^11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.36 
    @mui/core-downloads-tracker:  5.15.10 
    @mui/material: ^5.15.10 => 5.15.10 
    @mui/private-theming:  5.15.9 
    @mui/styled-engine:  5.15.9 
    @mui/system:  5.15.9 
    @mui/types:  7.2.13 
    @mui/utils:  5.15.9 
    @types/react: ^18.2.48 => 18.2.48 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^5.3.3 => 5.3.3 

Search keywords: TablePagination slots slotProps

[siriwatknp]

cc @DiegoAndai should we have another umbrella to take care of the completeness of slots and slotProps as a follow-up from the deprecation? I can own this if you'd like.

[DiegoAndai]

Hey @quibaritaenperdresatrompe, thanks for the report! The button icon's slots are under the action slots, as they're slots of the TablePaginationActions component. So you can access them through, for example, MuiTablePagination.defaultProps.slots.actions.nextButtonIcon. Here's an example: https://stackblitz.com/edit/stackblitz-starters-5rgtos?file=src%2FApp.tsx.

I would mark this issue as expected by design.

For context, this was introduced in #39353.

cc @DiegoAndai should we have another umbrella to take care of the completeness of slots and slotProps as a follow-up from the deprecation? I can own this if you'd like.

@siriwatknp Yes, I think we should have an issue for that 🙌🏼 the goal would be to add any missing slots and slotProps that were not added due to a deprecation. Could you create that issue?

I'm also curious about what you think about the sidenote in #33797 (comment):

I realized that we made a mistake in that PR. It should be slotProps.actions.slotProps.firstButton.

For deep slots, what should be the usage? I'm thinking

• slots.<slot> to override one-level slots
• slotProps.<slot> to override one-level slot's props
• slotProps.<parentSlot>.slots.<childSlot> to override two-level slots
• slotProps.<parentSlot>.slotProps.<childSlot> to override two-level slot's props
• slotProps.<grandparentSlot>.slotProps.<parentSlot>.slots.<childSlot> to override three-level slots
• ...

I don't know if we have any more of these. If we go with that, then the current TablePagination implementation is incorrect as it shouldn't allow slots.actions.nextButtonIcon, the correct path should be slotProps.actions.slots.nextButtonIcon.

[siriwatknp]

For deep slots, what should be the usage? I'm thinking

Make sense to me for the time being but in v7, we should consider restructuring components to not have nested slots.

[DiegoAndai]

I think we should close this issue as expected and create a new one to remove nested slots in the future; what do you think?

[siriwatknp]

I think we should close this issue as expected and create a new one to remove nested slots in the future; what do you think?

Sounds good. The new issue could be an umbrella one that covers all existing components that contain nested slots.

[DiegoAndai]

I created the follow up issue, closing this one.