Skip to content
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

Filter Input Regression #28174

Open
3 tasks done
rscarborough1996 opened this issue Apr 22, 2024 · 0 comments
Open
3 tasks done

Filter Input Regression #28174

rscarborough1996 opened this issue Apr 22, 2024 · 0 comments
Assignees

Comments

@rscarborough1996
Copy link

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

image
image

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants