[Feature Request]: teal::init to return shinyApp instead of a list

[gogonzo]

teal::init to return "teal_app" object (simple S3 class). For this class we can have a print method which can look as follows:

print.teal_app <- function(x, ...) {
  cat("teal app <more information about the app>")
  shiny::shinyApp(x$ui, x$srv) 
}

Thanks to above "teal_app" object will preserve previous features (list of ui, server, ui_args, ... etc) and could be run without shinyApp(x$ui, x$server) . This would shorten the apps code:

# from
app <- teal::init(...)
shinyApp(app$ui, app$server)

# to
teal::init(...)

With the S3 class first and the second in above code would be possible.

Alternatively, print.teal_app could just print information about the app with note use shinyApp(x$ui, x$server) to run the app.

Please note that shiny works in very similar way
https://github.com/rstudio/shiny/blob/370ba1f288d3f759456ef3ef6e768ee1d7fda677/R/shinyapp.R#L552

[chlebowa]

Do you mean just adding shinyApp(ui = res$ui, server = res$server) as the return value of init?

Nothing will be broken due to this,

Besides the fact that you can't do shinyApp(app$ui, app$server) anymore, do I have this correct?

[pawelru]

This is a potentially breaking change and if done (which I am still not sure about) it would be better to go through the formal deprecation process

[gogonzo]

The idea doesn't make sense. Let's pay attention to #1448