u35253 commented on issue #27622: URL: https://github.com/apache/superset/issues/27622#issuecomment-2730703478
First of all, this seems to apply to single-sided and double-sided range sliders. # Fallback alternative One alternative is to create separate text filters that can receive free input (accepting integer and decimal values). These filters might be called MyFieldMin and MyFieldMax. These can have default values of empty or of some reasonable values wanted for initial filtering. Then, use those filter values as Jinja in the dataset. If they exist, do a >= and < to filter as needed. # Meta discussion on "How is this still not implemented?" I don't know, but to improve the upon the current (awkward/suboptimal) filter implementation for numerical ranges with large ranges as tracked in this issue (e.g., large chunk sizing and difficulty getting slider to precise in-between values), I imagine it would be necessary to 1. Identify a preferred design for the same inputs (select a numeric field and present its range) and 2. implement that, get it approved, make sure it passes tests, etc. Presumably, because Superset is an community open-source project, asking "why nobody has solved this open issue yet" is sort of like asking why _anything_ hasn't happened -- maybe because - someone needs to do it in order it to be done, - or other things have been higher priority, - or not a lot of noise is made about it or it is not that visible of an issue, - or people end up falling back on another solution, - and/or something else, etc. # Moving forward For (1) -- proposed design improvement -- I would think that a freeform text input field accepting numbers, positioned at the below-center position of each single-sided slider accepting numeric freeform input (or: one text input at each end, when it is a double-sided input), which then "jumps" the slider to that precise position inputted and "shows" that number (ideally as inputted [example: 2215 or 2,215] but, if easier to implemented or deemed more Superset-ish, conforming to the display format of the slider values [example: 2.2k]) would potentially be a solution design. For (2) -- getting to resolving the issue -- I am not really in a position to develop this at this time, but I do empathize with the "too large grained of numerical range input sliders and inability to get needed values from them, even for somewhat reasonable if admittedly large-ish ranges" issue; hence, the comment. -- 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: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
