-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fix #505 : Remove "empty filter" row #511
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above
I have replaced the string "Empty Filter" by an empty string, so the fact you see it makes me think you might have used the wrong branch. Is that possible ? |
It seems it is. No idea how that happened given that I even pushed a merge commit 6ba57ab 😵💫 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-
For source storages that do not have any corpus available, can we disablethe "+" button or potentially even remove it or the "Metadata Filters" section completely?
-
When selecting a source storage that has multiple corpora, selecting a corpus from the dropdown menu creates and empty filter that does not go away automatically
Screencast.from.2024-12-12.16-55-09.webm
This seems just like an UI issue, because the chat can be started with the row present and is correctly using no metadata filter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Pierre!
Fix #505 : Remove "empty filter" row
I have kept the line
if filter_row.key != NO_FILTER_KEY
as it is necessary to create a new chat after adding a first filter row, which appears empty by default. Run it and tell me what needs to be improved.