You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users are allowed to enter values into a filter that do not exist in the dropdown. As they type in their value, it will appear in the drop down for them to select.
In version 2.0.1, the value was always present as the user typed.
In versions 3.1.0 and 4.0.0, the select window constantly changes as the user type. As a new character is entered it will flash "no data", then SOMETIMES it will display what the user has typed. Sometimes it remains on "no data" and the user is unable to select their input.
While this is a small regression from earlier versions, there are still use cases where this is relevant. For instance (as in my case) jinja can be used to get values from filters and use it to influence the query.
How to reproduce the bug
Try inputting a value that does not exist into a filter using version 3.1.0 or newer. Keep typing one character at a time until the window settles on "no data"
Screenshots/recordings
These images are of the same filter, on the same dashboard. I just retyped the last number until the result did or did not show up.
Superset version
4.0.0
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
Bug description
Users are allowed to enter values into a filter that do not exist in the dropdown. As they type in their value, it will appear in the drop down for them to select.
In version 2.0.1, the value was always present as the user typed.
In versions 3.1.0 and 4.0.0, the select window constantly changes as the user type. As a new character is entered it will flash "no data", then SOMETIMES it will display what the user has typed. Sometimes it remains on "no data" and the user is unable to select their input.
While this is a small regression from earlier versions, there are still use cases where this is relevant. For instance (as in my case) jinja can be used to get values from filters and use it to influence the query.
How to reproduce the bug
Try inputting a value that does not exist into a filter using version 3.1.0 or newer. Keep typing one character at a time until the window settles on "no data"
Screenshots/recordings
These images are of the same filter, on the same dashboard. I just retyped the last number until the result did or did not show up.
Superset version
4.0.0
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: