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
{{ message }}
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
In light of the recent template changes -- especially to form widgets where you've pulled the HTML structure out of the class and into the template file (which is awesome) -- I wish the same could be done with the pagination template.
Right now the first/prev/next/last links are in the template, but the HTML for the individual page links are generated inside the pagination class and passed into the template as a string, so they can't be customized without regex or extending the class.
It would be nice if they were passed as an array and generated via a foreach loop in the template file. Many of the other navigation templates (e.g. page & article navigation, breadcrumbs, news & event menus) are handled in this manner. Thanks!
The text was updated successfully, but these errors were encountered:
In light of the recent template changes -- especially to form widgets where you've pulled the HTML structure out of the class and into the template file (which is awesome) -- I wish the same could be done with the pagination template.
Right now the first/prev/next/last links are in the template, but the HTML for the individual page links are generated inside the pagination class and passed into the template as a string, so they can't be customized without regex or extending the class.
It would be nice if they were passed as an array and generated via a foreach loop in the template file. Many of the other navigation templates (e.g. page & article navigation, breadcrumbs, news & event menus) are handled in this manner. Thanks!
The text was updated successfully, but these errors were encountered: