2
87%
master: 87%

Ran 19 Apr 2020 06:27PM UTC

Files 14

Run time 1s

Badge

Embed ▾

Committed 19 Apr 2020 06:22PM UTC coverage: 87.347% (-11.5%) from 98.867%

Job # _R_CHECK_TESTS_NLINES_=0

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

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.

Run Details

856 of 980 relevant lines covered (87.35%)

14.19 hits per line

mong / tmongr / 1191 / 2
87%
master: 87%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1191.2 (_R_CHECK_TESTS_NLINES_=0)

mong / tmongr / 1191 / 2 87% master: 87%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1191.2 (_R_CHECK_TESTS_NLINES_=0)

mong / tmongr / 1191 / 2
87%
master: 87%

README BADGES
x