mjfrigaard / shiny-app-pkgs

Shiny app-packages

Shiny App-Packages
Explore the screenshots »

Report a Bug · Request a Feature . Ask a Question

---

About

Shiny App-Packages covers how to create a Shiny application as an R package.

Screenshots

Testing Shiny apps	Shiny frameworks

Built With

Quarto, Shiny and Posit workbench.

Getting Started

Make sure you have R, Posit Workbench, and Git installed.

Prerequisites

The contents of the text assumes you're comfortable with R, Posit Workbench, Shiny, and the tidyverse. Maybe you haven't built a ton of applications, but you understand reactivity, and you're comfortable with the core Shiny concepts (i.e., the UI, server, *_Input(), *_Output(), and render_* functions, etc.).

Usage

The code examples can be found in the moviesApp repo. The sections from each chapter can be found in the branches.

git checkout <branch>

Issues

See the open issues for a list of proposed features (and known issues).

• Top Feature Requests (Add your votes using the 👍 reaction)
• Top Bugs (Add your votes using the 👍 reaction)
• Newest Bugs

Reach out to the maintainer at one of the following places:

• GitHub issues
• Contact options listed on this GitHub profile

Project assistance

If you want to say thank you or/and support active development of Shiny App-Packages:

• Add a GitHub Star to the project.
• Tweet about the Shiny App-Packages.

Together, we can make Shiny App-Packages better!

Contributing

First off, thanks for taking the time to contribute! Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make will benefit everybody else and are greatly appreciated.

Authors & contributors

The original setup of this repository is by Martin Frigaard.

Acknowledgments

This book is the result of multiple discussions with 1) Shiny developers who were new to writing R packages, 2) R package authors who were learning Shiny development and testing, and 3) new R users who wanted to build a robust and scalable application. Shiny App-Packages wouldn't have been possible without the contributors below (and I am deeply grateful for all of their help!).

• Henry Bernreuter & Elizabeth Marshallsay for the initial discussions that created the outline for this book
• Andrew Bates for being an exemplary developer and professional, quietly building outstanding UIs, applications, and packages
• Eric Simms for asking so many great questions, reviewing chapters, and giving phenomenal feedback
• Eric Nantz¹ for his R podcast, Shiny developer series, workshops, and everything else he does for the Shiny community
• Philip Bowsher for everything he does for the R/Pharma conference and community
• Ted Laderas for his excellent gRadual intRoduction to Shiny course and insightful blog posts
• Jennifer Bryan and Hadley Wickham for their posit::conf(23) package development masterclass workshop.
• Maya Gans for having multiple conversations and Shiny modules and package dependencies
• Leon Samson for his feedback on the testing chapters

For a full list of all authors and contributors, see the contributors page.

License

This project is licensed under the MIT license.

See LICENSE for more information.

Footnotes

1. Eric's LinkedIn ↩

shiny-app-pkgs's Issues

Add introduction to BDD in the chapter "Test suite"

A small introduction to BDD in the chapter "Test suite", or a link to the BDD explanation in the appendix/ in the chapter "Specifications" (I think now it is only mentioned in the TLDR section of the "Test suite" chapter)

Minor fixes in Intro/Welcome

how and when to use session$flushReact() when testing shiny servers/modules

A small example of how and when to use session$flushReact() when testing shiny servers/modules.

Check transitions at the end of each chapter

Dependencies links to launch, not data.

Add comparisons to golem and rhino (where they are relevant)

Rhino:

• In dependencies chapter
• When discussing modules

golem:

• External files
• DESCRIPTION (using usethis vs attachment)
• Documentation (@noRd

Resize cover image

Wayyyyy too big

Introduction - Shiny apps - Standalone app function: call to movies_app() not working

I think it is too soon for the call to movies_app() .... does not work for me. Would this not need load_all(), which we can't do yet? I can make the app run with the "Run App" button in the app.R edit pane.

Thoughts on creating Shiny app validation reports?

This is not an issue but rather a question.

I am developing a Shiny application that needs to be validated and I am using BDD unit-testing following the recommendations in your online book. For me personally, a section about how to create validation reports for shiny applications would be great addition for the book and if you would ever find the time to include that, I think it would be more than helpful.

For example, is it possible to extract the descriptive text in the unit tests and the outcome of the tests into a validation report (HTML or PDF)? I am aware of the valtools package, but I am not sure if that is compatible with this workflow. I would love to hear your opinion about that. Do you have any thoughts on how this can be done, or any recommendations?

Introduction - Shiny apps - Standalone app function: rsconnect directory

03_projApp and my own workspace do not have an rsconnect directory:

Create sections for containers/deployment

Docker, aws, etc.

test_that desc with line breaks causes expect_snapshot to always be overwritten.

Perhaps good to know that long descriptions in testthat::describe() or testthat::test_that(), as for example here, cause issues with testthat::expect_snapshot() for me. See the issue that I opened here.

shinytest2 with a shiny app created in the golem framework

An example of how to use shinytest2 with a shiny app created in the golem framework (I think it does not work out of the box since it needs an app.R file in the package directory?)

Loading packages for initial movies app is tripping me up

When I select Run App, I get this pop-up:

If I select "Yes":

If I try again and select "No":

packages.qmd typos, etc.

Add section on keyboard shortcut for testing and coverage

Test active file, coverage for active file

Write tests for rhino branch

testthat and cypress tests

Create section on complex storage / bookmarking

"Did you have a section on complex storage / bookmarking? Would love to see others strategies with that."

example of how to use the BDD syntax (the describe() and it() functions) with a testServer() object

Include a code example of how to use the BDD syntax (the describe() and it() functions) with a testServer() object in the chapter "Test Modules"

code snippet in Rstudio for BDD describe() and it() functions

A tip somewhere in the book that you can add a code snippet in Rstudio for BDD testing with the describe() and it() functions (I found this to be quite helpful)

Introduction - Shiny apps - Updated movies app project contents: Confusion with comments and first showcase results

What needs to be commented out in the app.R header after installing? The pkgs and install.packages lines? What about the library statements? Commenting the load("movies.RData") line makes the app crash. Not commentiing the source("utils.R") makes it crash.

With Showcase, you display this:

But what I am seeing with my best guess commenting is this:

You have movies_app <- function .... I don't have that. You don't have anything of the load("movies.RData") and source("utils.R") ... looks like those lines were removed at some point. I think you are showing code a couple of steps ahead of where it is when I am following your guide.