Default @posts to main query and accept query arg #1
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.
Thanks for this set of directives, @Log1x!
For your consideration...
This PR changes
@posts
to provide greater flexibility:$query
This would break backwards compatibility with previous
@posts
usage that defaulted to using$query
.Options for moving forward:
@posts
->@posts($query)
)$query
exists it defaults to that instead of to the main queryUpdated docs:
@posts
@posts
begins the post loop. It is wrapped in ahave_posts()
conditional and thus will returnnull
if no posts are found.@endposts
is available to end your loop andhave_posts()
conditional as well as resetting your loop withwp_reset_postdata()
.@posts
defaults to the main query, but it accepts aWP_Query
instance as an optional argument. If the argument is provided,@posts
will use that query instead.