This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
Add initial support for previewing meta queries #174
Merged
Conversation
This file contains 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
Release 0.6.1
Fix build for 0.6.1
Fix location of readme change
…omize-posts into feature/meta-queries
…nto feature/meta-queries-update
…nto feature/meta-queries
…to feature/meta-queries
…omize-posts into feature/meta-queries-update
Improve meta query support
Customize preview: Allow filtering of array meta values.
Skip meta query compare if meta value is array and compare type is not 'IN'
…nto feature/meta-queries
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I am very aware that we are woefully under-supporting the various query vars that a
WP_Querycan take and which can be impacted by the Customizer state. Moreover, I am even more concerned that we are not properly accounting for combinations of query vars and considering when two conditions cancel each other out. A much more robustposts_wherequery builder is needed I think.