villebro opened a new pull request, #30062: URL: https://github.com/apache/superset/pull/30062
### SUMMARY While working on a Jinja time filtering feature, I noticed a curious quirk in how `get_since_until_from_time_range` works: - When `time_range="No filter"` it returns `(None, None)` for `since` and `until` respectively - For `time_range=None` it returns `(None, datetime(current_date))` I don't see any reason for this, and can only assume it's a quirk of how the complex function works for other more intricate time ranges. Therefore, I feel it prudent to change the behavior, so that `None` and `"No filter"` both returns the same value. Let's see if this change breaks some tests - if not, I can only assume this isn't intended, but rather an artifact of the current logic. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF <!--- Skip this if not applicable --> ### TESTING INSTRUCTIONS <!--- Required! What steps can be taken to manually verify the changes? --> ### ADDITIONAL INFORMATION <!--- Check any relevant boxes with "x" --> <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue --> - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] 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 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
