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
One slightly tricky thing when generating pagination URLs is keeping all the other query string parameters besides page. It could be a nice option to have cbpaginator generate those for you for prevURL and nextURL. This would require a new method argument of the current url to generate the links from. We could wire this up automatically in ColdBox, but other users would need to either provide it themselves, use a default (maybe in the CGI scope), or use a pagination method that doesn't generate links. This would probably be another option alongside generateSimple.
The last idea with this is that we maybe want to generate the links in-between, like so:
Not sure how we would know what pages the user wanted generated, so maybe that's a separate ticket.
The text was updated successfully, but these errors were encountered:
Generating HTML/CSS (and adding other URL options) may be beyond the scope of this internal query object modifier.
If you want to generate HTML-based navigation, pagination.cfc (the "premier paging library for ColdFusion programmers") is available to perform that function for you. https://www.dopefly.com/projects/pagination/
One slightly tricky thing when generating pagination URLs is keeping all the other query string parameters besides page. It could be a nice option to have cbpaginator generate those for you for
prevURL
andnextURL
. This would require a new method argument of the current url to generate the links from. We could wire this up automatically in ColdBox, but other users would need to either provide it themselves, use a default (maybe in the CGI scope), or use a pagination method that doesn't generate links. This would probably be another option alongsidegenerateSimple
.The last idea with this is that we maybe want to generate the links in-between, like so:

Not sure how we would know what pages the user wanted generated, so maybe that's a separate ticket.
The text was updated successfully, but these errors were encountered: