mui / mui/material-ui

[TablePaginationActions]: Add ability to add a component between the left navigation and right navigation in TablePaginationActions.

Open
#43,409 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: TablePagination customization: dom scope: table type: enhancement
Dominant language
JavaScript
Stars
99.1k
Forks
32.5k
Avg merge
2d 17h
Merged PRs (30d)
106

Description

Summary

The default ActionsComponent for TablePagination is TablePaginationActions which renders the page navigation buttons. If TablePaginationActions can accept a custom component as a prop to render between the left navigation and right navigation, TablePaginationActions can be used to create a custom Action Component.

Examples
Screen Shot 2024-08-22 at 1 08 06 PM
Motivation

We have a design to add a TextField between the Left Navigation and Right Navigation to enter the page number.
Currently, there is no way to add this TextField component in TablePaginationActions. We have to fork the TablePaginationActions component and add the TextField.
If MUI can provide a prop to add a component between the left navigation and right navigation in TablePaginationActions, we can avoid the fork.

Search keywords: TablePaginationActions

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the TablePaginationActions entry point and reviewing how its left and right navigation controls are rendered. Determine the prop shape and placement needed for a custom component between them, then verify that the component can be used by TablePagination without forking the default actions.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.