You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] bug report => Search github for a similar issue or PR before submitting
[ x] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
Current behaviour
There is a simple pagination with buttons and not information about total pages and/or records.
Expected behavior
Allow templating to provide custom displays for extra pagination info.
For example:
Would right now show total records and current page records ( with 100 records per page it would be 1-100 of 1000, next page 101-200 of 1000).
Make this possible through custom templating (providing access to required paginator values).
Optionally could make the whole paginator section templateable so custom paginator designs could be implemented.
The text was updated successfully, but these errors were encountered:
@cagataycivici Is there a fix for rowsPerPageOption for 'ALL' in case user wants to display all records on Datatable (without pagination). This is highly needed in a project i'm working on. If not yet implemented, is there a work around you can suggest? Thanks
Current behaviour
There is a simple pagination with buttons and not information about total pages and/or records.
Expected behavior
Allow templating to provide custom displays for extra pagination info.
For example:
Would right now show total records and current page records ( with 100 records per page it would be 1-100 of 1000, next page 101-200 of 1000).
Make this possible through custom templating (providing access to required paginator values).
Optionally could make the whole paginator section templateable so custom paginator designs could be implemented.
The text was updated successfully, but these errors were encountered: