[5.5] Allow to automatically use where/whereIn or whereNot/whereNotIn methods in DatabaseRule #20739
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.
This adds additional improvement to where/whereIn and whereNot/whereNotIn methods in
DatabaseRule
trait. If you don't know what exactly is value (array or string) probably we don't want to force user to write code like this:If merged, in such case either
where
orwhereIn
can be used with exact same result. It will be especially useful if request data is used as value.