problem with optimized FILTER_AS_MATCH strategy
limejuly opened this issue · comments
Back ground: version 1.2.0, using FILTER_AS_MATCH strategy
Problem: Querying any argument that is not "filter" will be ignored.
for example, what I query is:
{
product(id:"product8") {
id
}
}
And the "id" argument is ignored.
In the previous version, non filter arguments will make FILTER_AS_MATCH fail, so one can fall back to normal strategy. But now it is not failing, neither does it handle them.
Is that the expected behavior or am I using it wrong?
The corresponding change is #153
@limejuly can you create a test case for your issue please