You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving the processArray() won't give the expected result, for example if one use 'boost' => 2.0 he expect it to be at the FieldLevel (i.e. 'field' => ['boost' => 2.0, ...]) so this processArray() should stay here...
I guess the best is to get 2 array of parameters:
FieldParameters: That will be used at FieldLevel, and remains in constructor
QueryParameters: That would be used at QueryLevel (and get accessed only via accessors ? or last param in constructor ?)
Then in the process of building the array this will be generated
For some query like the
RangeQuery
or theTermQuery
an extra parameter like_name
(used for Named Queries) won't be at the top level.Example:
This is due to the use of parameters as query parameters and not extra ones
ElasticsearchDSL/src/Query/TermLevel/RangeQuery.php
Line 72 in 197eedd
It's the same for
TermQuery
ElasticsearchDSL/src/Query/TermLevel/TermQuery.php
Line 70 in 197eedd
I think here the
processArray()
should be called after...This works with a Terms query:
The text was updated successfully, but these errors were encountered: