Closed hairmare closed 8 years ago
I'm seeing unexpected globs in FIQL based eq() searches. I'm testing with rql rql:parser 'name=eq=*'
eq()
rql rql:parser 'name=eq=*'
query └─ query └─ eq ├─ name └─ //i
I was expecting the following result.
query └─ query └─ eq ├─ name └─ "*"
Is this a case of me expecting the wrong thing or actually a parser bug?
The same thing also seems to happen with rql rql:parser 'name=*'. I might make sense to expect the following result in this case.
rql rql:parser 'name=*'
query └─ query └─ like ├─ name └─ //i
edit: This is not related to FIQL as rql rql:parser 'eq(name,*)' does the same thing...
rql rql:parser 'eq(name,*)'
Actually I'm wondering why there is an extra Glob class. Why not just keep the string? The possibility to convert a glob to a regex could be provided in a utility class for those who need it.
I'm seeing unexpected globs in
FIQL basedeq()
searches. I'm testing withrql rql:parser 'name=eq=*'
I was expecting the following result.
Is this a case of me expecting the wrong thing or actually a parser bug?
The same thing also seems to happen with
rql rql:parser 'name=*'
. I might make sense to expect the following result in this case.edit: This is not related to FIQL as
rql rql:parser 'eq(name,*)'
does the same thing...