fix(queryContent
): use path argument as prefix if there is another condition
#1612
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.
π Linked issue
resolves #1565
β Type of change
π Description
Currently if user passes the path argument to
queryContent
composable and callfindOne
, it will look for the exact match for that path.This is acceptable behaviour, when user wants to find a single content without additional condition.
But when user provides another condition using
where
function, we should use the path as a prefix matcher, otherwise the result will be empty all the time.π Checklist