IBX-7126: Allowed passing extra parameters to pager of "My Drafts" tab #1012
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v4.6
When "My Drafts" Dashboard tab is rendered as a Customizable Dashboard Builder block, neither original request route name nor pagination parameter is available in a current context.
Parameters, in the end, after a few iterations, were seamlessly copied from main request to the block-rendering request via https://github.com/ibexa/dashboard/pull/53.
This PR allows merging extra Pagerfanta options coming from a template (see https://github.com/ibexa/dashboard/pull/53 for usage - passed extra
routeName
) with current rendering options.Because of high coupling between MyDraftsTab and Twig Environment, I needed to stub Twig Environment to add test coverage for the change.
TODO
pager_options
Checklist:
$ composer fix-cs
).