Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for shiny progress indicator based on the RStudio complex example. This pull request directly addresses issue #305 and partially addresses issue #272.
Comments were used in the travis yaml to avoid a pull-irrelevant build error involving deployment keys back to Github. I guess this change also resulted in the codecov errors. These changes can and should be ignored.
Progress message and detail were coded to best match the
progress::progress_bar
message usingprettyunits::vague_dt()
, but the decision to includeprettyunits
as a dependency is left up for debate. As it stands now, the user will have tolibrary(prettyunits)
in their app code to make this work.This solution also requires the length of the progress bar in frames to be determined and set when making the
shiny::Progress
object and this value should also be passed toannimate()
.Example app: