[Paginator] Add jump-to-page functionality
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
#### Bug, feature request, or proposal:
Feature request
#### What is the expected behavior?
To be able to jump to a specific page using a dropdown populated with page numbers. The dropdown should be next in line after the `Items per page` dropdown, so you can choose the page size and then the page number you want to go to.
Don't know if the following part is smart, but in use cases where the page number is large, a `step` input can be implemented. If the total number of pages is 500, and the step is 5, the `Page number` dropdown would hold only pages 1, 5, 10, 15, 20 .... so the user can get to the desired page in as little scrolling and as few clicks as possible.
#### What is the current behavior?
To get to a specific page you have to go page by page
#### What is the use-case or motivation for changing an existing behavior?
In my case, I have a 100 item per page list, that has 3500 total items sorted by date and the users land at the last page. If the users wants to check the items that were added at the beginning of the year, they know that they should be looking at items from 1 to at least 300, so that is 32 clicks to get to the desired items. As the total page count gets bigger, the harder it is to get to the last pages (first pages in my case).
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le point d’entrée du paginator Angular et examinez comment la liste déroulante existante « Items per page » est rendue et reliée à la navigation entre les pages. Examinez la liste déroulante demandée pour les numéros de page, son emplacement et le comportement facultatif de pas ; le travail est considéré comme terminé lorsque les utilisateurs peuvent sélectionner directement une page précise sans avancer page par page.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 30/100