fix: Fixed numeric filtering issue in Superset

[Sayan199]

SUMMARY

Fixes #33206

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

In order to test this, we need to

1. Add a filter for a numeric field that contains both integer and decimal values (e.g., 21, 21.8, 25.35, etc.).
2. First select an integer value (for example, 21) in the filter, and then fractional values.
   This should now be able to filter and give results that do match with 21 but also with 21.8 and 25.35

ADDITIONAL INFORMATION

• Has associated issue: Incorrect filtering for numeric values with different decimal precision #33206
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[korbit-ai]

Review by Korbit AI

Korbit automatically attempts to detect when you fix issues in new commits.

Category	Issue	Status
	Missing temporal range value handling explanation ▹ view	🧠 Not in standard

Files scanned

​

File Path	Reviewed
superset/models/helpers.py	✅

Explore our documentation to understand the languages and file types we support and the files we ignore.

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

[rusackas]

Looks like there are a bunch of CI tasks failing, but we should probably start by running pre-commit to fix the linting/formatting issues, and see if anything else gets unblocked.

Superset uses Git pre-commit hooks courtesy of pre-commit. To install run the following:

pip3 install -r requirements/development.txt
pre-commit install
A series of checks will now run when you make a git commit.

Alternatively it is possible to run pre-commit by running pre-commit manually:

pre-commit run --all-files

[michael-s-molina]

Possible duplicate of #33230