Open fmassot opened 6 months ago
This problem comes from the 3rd party parser we use to power the linter on the frontend. Its grammar doesn't support /
in field names.
It does not impede the ability to execute the query, query runs are separated from linting.
Long term problem is that this dependency is unmaintained and relies on an unmaintained parser generator itself. We should probably maintain our own parser if there's no better option out there.
I don't know if that's actually a good idea, but tantivy query parser is pretty self contained, and shouldn't be too hard to integrate as a wasm module in a js app
I have the same issue here with the 'IN' https://quickwit.io/docs/reference/query-language#term-set-fieldin-a-b-c