Pagerfanta updates #177
Merged
Pagerfanta updates #177
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
We have to fix the main build before we can go anywhere further. |
Closed
pamil
approved these changes
Oct 14, 2020
Contributor
|
Thank you, Michael! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As noted here, the latest version of the Pagerfanta package was restructured to support separately installed sub-packages. So, to help with avoiding deprecation notices and preparing for compatibility with the new major version I expect to push out toward the end of the year, I've bumped the Pagerfanta minimums up to the latest versions, updated the query adapter classes to use the non-deprecated classes, and changed the component to install only the
pagerfanta/coresub-package since that's all it directly depends on.