-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
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
Search completion issue when searching payee: field with unescaped *
character
#1846
Labels
Comments
Yeah, I guess we need to escape those suggestions. A PR with a fix would be welcome. |
I've found where to modify the generated suggestion but didn't have time to actually test. I'll send the PR in the next weeks hopefully! |
alexandre-janniaux
added a commit
to alexandre-janniaux/fava
that referenced
this issue
Sep 20, 2024
When inserting a suggestion, the value can have invalid characters, and in particular `*` which can easily be present on the payee: field or narration field. Fixes beancount#1846
alexandre-janniaux
added a commit
to alexandre-janniaux/fava
that referenced
this issue
Sep 20, 2024
When inserting a suggestion, the value can have invalid characters, and in particular `*` which can easily be present on the payee: field or narration field. Fixes beancount#1846
Fixed in a45e7f6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I've met an issue with the search completion where it suggests an unescaped string (I'm searching for "leroy"):
leading to the account being empty
If I escape the string correctly, I do get the correct payee subacount:
Tested on fava-1.29.dev3+g365cd5dc
The text was updated successfully, but these errors were encountered: