Reactive input private$currentThemeDependency is shown at the output
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, r
- Domain
- data-visualization
Research direction
Run the provided R Shiny example with reactlog enabled and inspect the visualization that places nodes in input and output sections. Trace how private$currentThemeDependency is classified for display. Done means this input node appears in the input section rather than the output section.
Written by the indexing model from the issue text.
Description
With the changes from https://github.com/rstudio/shiny/pull/3116, a new input node private$currentThemeDependency is introduced which is expected as mentioned by @wch in https://github.com/rstudio/shiny/pull/3160.
However, this node is displayed at the output section instead of at the input section
Steps to reproduce:
- Run the following example
library(shiny)
# Enable reactlog
library(reactlog)
reactlog_enable()
ui <- fluidPage(
titlePanel("Hello Shiny!"),
sidebarLayout(
sidebarPanel(
sliderInput(inputId = "bins",
label = "Number of bins:",
min = 1,
max = 50,
value = 30)
),
mainPanel(
plotOutput(outputId = "distPlot")
)
),
### start ui module
reactlog_module_ui()
### end ui module
)
server <- function(input, output, session) {
x <- faithful$waiting
bins <- reactive({
seq(min(x), max(x), length.out = input$bins + 1)
})
output$distPlot <- renderPlot({
hist(x, breaks = bins(), col = "#75AADB", border = "white",
xlab = "Waiting time to next eruption (in mins)",
main = "Histogram of waiting times")
})
### start server module
reactlog_module_server()
### end server module
}
shinyApp(ui = ui, server = server)
- Notice that as highlighted in the snapshot below,
private$currentThemeDependencydespite being input value, its shown at the output section
- Dominant language
- JavaScript
- Stars
- 131
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rstudio/reactlog
-
ai-generated-issue
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
All issues in rstudio/reactlog
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100