Jakub Sobolewski

@rszymanski I tested the component using `examples/calendar_range/app.R` and it seems like `max` doesn't prevent you from selecting a greater value. Works after you update it from server though. `min` works...

Thanks @simon-tarr! I agree, there's definitely a room for improvement in the tutorial. We're currently mostly focused on releasing the package on CRAN to make it available for broader audience....

Hello @simon-tarr, thanks for reaching out! Does this happen only in Chrome or in other browsers as well? I've checked the app on the same R version, clean `renv` with...

Running the example with shiny.react 0.1.0 throws the same error. In both cases it's thrown by a Leaflet in JSX context (`leafletOutput("mymap")`).

No clue at the moment. But I've found that when I'm using `uiOutput` and `renderUI`, in both following approaches, it doesn't throw the error ``` Stack( uiOutput("mapSlot") ) output$mapSlot

Hi @shahreyar-abeer, The only way I found to update a slider using this approach is to create the slider on server side: ```r library(shiny) library(shiny.fluent) shinyApp( ui = tagList( uiOutput("sliderPlaceholder"),...

`R CMD check --as-cran` reports: - 1 warning, mostly `Undocumented arguments in documentation object {Component}` and `Documented arguments not in \usage in documentation object {Component}` - 3 notes: - package...

When components are generated using `shiny.fluent:::component` factory the `...` argument is not documented which results in e.g. `Undocumented arguments in documentation object 'Toggle' ‘...’`. It can be resolved using e.g....

Hi @corinabioinformatic, submitting the package to CRAN is still in progress, but you can always install the package from GitHub using: ``` remotes::install_github("Appsilon/shiny.react") remotes::install_github("Appsilon/shiny.fluent") ```

To close this issue those must be closed first: - [x] #122 - [x] #128 - [x] #99