-
-
Notifications
You must be signed in to change notification settings - Fork 46
Redesign and change position of reporter options #1562
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
base: main
Are you sure you want to change the base?
Conversation
Unit Tests Summary 1 files 26 suites 2m 10s ⏱️ Results for commit 1c28236. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 5a81632 ♻️ This comment has been updated with latest results. |
Code Coverage Summary
Diff against main
Results for commit: 1c28236 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Not sure if it fits here, but the ![]() I'm applying the following patch on #1559 as this is picked by e2e tests, but it also fits in this PR diff --git a/R/reporter_previewer_module.R b/R/reporter_previewer_module.R
index 19b707b34..758c1736c 100644
--- a/R/reporter_previewer_module.R
+++ b/R/reporter_previewer_module.R
@@ -43,6 +43,7 @@ reporter_previewer_module <- function(label = "Report previewer", server_args =
# This is to prevent another module being labeled "Report previewer".
class(module) <- c(class(module), "teal_module_previewer")
module$label <- label
+ module$path <- label
attr(module, "teal_bookmarkable") <- TRUE
module
} |
@@ -103,6 +102,39 @@ srv_teal <- function(id, data, modules, filter = teal_slices()) { | |||
shinyjs::showLog() | |||
} | |||
|
|||
insertUI( |
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.
why to insertUI
when elements don't use any objects created in the server. I think this can be moved to UI directly
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.
These ui elements need to be placed in a different level than the current shiny module where they are called. The need to be placed inside the ui_teal_modules_nav()
but since it is called in a different shiny module we are inserting by referencing the selector of that element.
Companion of insightsengineering/teal.reporter#360