mong / tmongr / 1191

87%

push

travis-ci

Use moduleServer instead of callModule setup (#89)

`testModule` is no longer a part of `shiny`, so we have to use `testServer` to test our modules. `callModule` way of running modules and regular functions way of making modules can not be tested by `testServer`. Thus, we have to use `moduleServer` to make modules (and run the modules as regular functions). This is also the recommended way according to `?shiny::callModule`:

> Starting in Shiny 1.5.0, we recommend using moduleServer instead of callModule, because the syntax is a little easier to understand, and modules created with moduleServer can be tested with testServer().

In practice I have replaced all
```R
mymodule <- function(input, output, session, arg1, arg2) {
```
with
```R
mymodule <- function(id, arg1, arg2) {
   shiny::moduleServer(id, function(input, output, session) {
```
in the module part, and replaced all
```R
shiny::callModule(mymodule, "myID", arg1 = "blablabla", arg2 = "blablabla2")
```
with
```R
mymodule("myID", arg1 = "blablabla", arg2 = "blablabla2")
```
where we call modules.

32 of 32 new or added lines in 4 files covered. (100.0%)

856 of 980 relevant lines covered (87.35%)

14.19 hits per line