Default to an empty array for get_pagination #1782
Merged
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.
Ticket: #1758
Issue
If a user is going to call
Timber\Pagination\get_pagination
they need to do so with an argument, even an empty oneThis is likely because the preferred method is:
Solution
This isn't a good solution (even calling
\Timber\Pagination
directly is generally not recommended). But it was in the starter theme for years this way (and tutorials, etc.) so I think we should make this less preferred method as easy-as-possible.Impact
None.
Usage Changes
Nope.
Considerations
Ideally consider making
Pagination
a protected class that can't be called directly. If someone wants pagination they almost certainly want the posts with them. Closing off this external access point in3.x
or something might be the best way to ultimately resolveTesting
None, but backwards compatibility behavior should be caught by prior tests