-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
fixes the relationship between module_specific
and mapping
.
#968
Conversation
Code Coverage Summary
Diff against main
Results for commit: 54b8324 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Test Performance DifferenceAdditional test case details
Results for commit 6275ace ♻️ This comment has been updated with latest results. |
#' If `module_specific` is not provided, its value is inferred based on the `mapping` parameter: | ||
#' - If `mapping` is provided and non-empty, `module_specific` is set to `TRUE`. | ||
#' - If `mapping` is missing or empty, `module_specific` defaults to `FALSE`. | ||
#' This behavior allows for dynamic determination of filter panel specificity based on the provided `mapping`. |
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.
#' This behavior allows for dynamic determination of filter panel specificity based on the provided `mapping`. |
@@ -14,6 +14,11 @@ | |||
#' of filters specified - see `mapping` argument. | |||
#' - `FALSE` when one filter panel needed to all modules. All filters will be shared | |||
#' by all modules. | |||
#' Note: This parameter does not have a default value and should be explicitly provided. |
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.
#' Note: This parameter does not have a default value and should be explicitly provided. |
#' If `module_specific` is not provided, its value is inferred based on the `mapping` parameter: | ||
#' - If `mapping` is provided and non-empty, `module_specific` is set to `TRUE`. | ||
#' - If `mapping` is missing or empty, `module_specific` defaults to `FALSE`. |
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.
#' If `module_specific` is not provided, its value is inferred based on the `mapping` parameter: | |
#' - If `mapping` is provided and non-empty, `module_specific` is set to `TRUE`. | |
#' - If `mapping` is missing or empty, `module_specific` defaults to `FALSE`. | |
#' Defaults to `TRUE` if `mapping` provided, otherwise to `FALSE`. |
@@ -5,6 +5,7 @@ | |||
* `data` argument in `init` now accepts `teal_data` and `teal_data_module`. | |||
* Added `landing_popup_module` function which creates a module that will display a popup when the app starts. The popup will block access to the app until it is dismissed. | |||
* Filter state snapshots can now be uploaded from file. See `?snapshot`. | |||
* Removed default value for `module_specific` from `teal_slices`, now dynamically determined based on mapping content—if mapping is provided and non-empty, `module_specific` defaults to `TRUE`, otherwise to `FALSE`. |
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.
* Removed default value for `module_specific` from `teal_slices`, now dynamically determined based on mapping content—if mapping is provided and non-empty, `module_specific` defaults to `TRUE`, otherwise to `FALSE`. | |
* Removed default value for `module_specific` argument in `teal_slices`. The default value now depends on the `mapping` argument. |
closing this PR based on comment #966 (comment). |
fixes: #966
Example