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
KNP Paginator Bundle heavily relies on Symfony's Request (mostly "->query") object. I would like to step away from this and integrate a mechanism to supply the whole Bundle with something like a UserDefinedRequest - which supplies the Bundle (meaning every class that relies on Symfony's Request object) with all necessary functions (mainly those supported by InputBag). This way, the application can specify where the parameters come from (other than the Request->query object).
Why? Just one example: currently, URLs look like ?sort=a.fancy_title, but i do not whant to show everybody the table column names, instead I would like to set up a URL like ?sort=title and map the value title in the controller to a.fancy_title and pass it to Paginator.
Is this already possible? If not: how can I archieve this?
Thanks in advance
Gregor
The text was updated successfully, but these errors were encountered:
Bundle version ^5.8
Symfony version 5.4
Support Question
KNP Paginator Bundle heavily relies on Symfony's Request (mostly "->query") object. I would like to step away from this and integrate a mechanism to supply the whole Bundle with something like a UserDefinedRequest - which supplies the Bundle (meaning every class that relies on Symfony's Request object) with all necessary functions (mainly those supported by InputBag). This way, the application can specify where the parameters come from (other than the Request->query object).
Why? Just one example: currently, URLs look like ?sort=a.fancy_title, but i do not whant to show everybody the table column names, instead I would like to set up a URL like ?sort=title and map the value title in the controller to a.fancy_title and pass it to Paginator.
Is this already possible? If not: how can I archieve this?
Thanks in advance
Gregor
The text was updated successfully, but these errors were encountered: