-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Altering the order of first/previous and last/next #83
Comments
Ah hmmm yeah, thats not configurable. How would you suggest making that configurable? I'm not sure if we should introduce an order tuple or not, something like |
What about a param something like <%= pagination_links @page, distance: 1, edge: "outside" %> meaning that the "edge" page elements (first and last) would be forced to the outside positions as requested above. Default would be edge: "inside". |
I'm not sure that |
|
I think something like Though I still don't see why an order tuple wouldn't also work. |
If I wanted to do something like this
it would generate
but I would want to generate
Another enhancement that I don't think is currently possible is always showing the previous/next buttons but mark them as disabled if on the first/last page respectively.
The text was updated successfully, but these errors were encountered: