-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
503 shinytest2 fixes bug with setting numeric range #1152
503 shinytest2 fixes bug with setting numeric range #1152
Conversation
Code Coverage Summary
Diff against main
Results for commit: c097183 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 26 suites 1m 30s ⏱️ Results for commit c097183. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit f2917ba ♻️ This comment has been updated with latest results. |
shinyWidgets
limitation
shinyWidgets
limitation00c9973
to
66a3fdd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM!
Pull Request
Fixes #1151
Changes description
shinyWidgets::numericRangeInput
uses a custom handler and seems to require ajs: Shiny.setInputValue
callChange of explicit arguments in{s,g}et_active_filter_selection
totype
to reflect this logic and allow for further extensions.is_numeric
argument in favor of auto-detection of slice type (categorical / numerical range){s,g}et_active_filter_selection