[PATCH] Fix find()'s docs on nested subconditions
The documentation says that you need to write (P & Q) | R
like this:
{
'conditions': [
{
'query': {
'conditions': [P, Q],
'operator': '&'
}
},
R
],
'operator': '|'
}
but actually you need to omit the { 'query': ... } wrapping the
subclause. Including it crashes parseCondition() at:
v = condition['value']
for the obvious reason.
This commit is contained in:
parent
58f6c9901d
commit
9ac5dc7ba9
1 changed files with 2 additions and 4 deletions
|
|
@ -112,10 +112,8 @@ def find(request, data):
|
|||
operator: string, // comparison operator, see below
|
||||
value: string // value
|
||||
}, { // ... and/or query objects (nested subconditions)
|
||||
query: {
|
||||
conditions: [object, ...], // list of condition objects
|
||||
operator: string // logical operator, '&' or '|'
|
||||
}
|
||||
conditions: [object, ...], // list of condition objects
|
||||
operator: string // logical operator, '&' or '|'
|
||||
}],
|
||||
operator: string // logical operator, '&' or '|'
|
||||
},
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue