We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I parsed the expression Category:"Logon and expected SearchField('Category', Word('"Logon')).
Category:"Logon
SearchField('Category', Word('"Logon'))
However i received luqum.exceptions.IllegalCharacterError.
luqum.exceptions.IllegalCharacterError
I parsed the expression Category:Logon" and expected luqum.exceptions.IllegalCharacterError.
Category:Logon"
However i received SearchField('Category', Word('Logon"')).
SearchField('Category', Word('Logon"'))
from luqum.parser import parser # No traceback tree = parser.parse('Category:Logon"') print(repr(tree)) # Traceback tree = parser.parse('Category:"Logon') print(repr(tree))
Is this an expected behavior ?
Shouldn't both expressions react in the same way ?
Is it related to this issue ? #86
The text was updated successfully, but these errors were encountered:
Yes it might be related. I'm not sure it's easy to fix with current parser.
Sorry, something went wrong.
Hi, any update about a potential fix of this issue?
Sorry I don't have time to work on it personally right now (maybe at beginning of 2023.
If you want to try to tackle it, I can take the time to point you in the right direction.
No branches or pull requests
Hi,
I parsed the expression
Category:"Logon
and expectedSearchField('Category', Word('"Logon'))
.However i received
luqum.exceptions.IllegalCharacterError
.I parsed the expression
Category:Logon"
and expectedluqum.exceptions.IllegalCharacterError
.However i received
SearchField('Category', Word('Logon"'))
.Is this an expected behavior ?
Shouldn't both expressions react in the same way ?
Is it related to this issue ? #86
The text was updated successfully, but these errors were encountered: