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.
Fixes part of #399
This PR:
renv
lock file which is pointing at fav2.2.1
(really old) tov0.5.0
v0.3.0
in favor of the recently releasedv0.5.0
v0.3.0
and instead re-focuses on installing a recent version when it detects the problematicv0.4.0
is installedv4.2.2
Note, once this if fixed, we can push through other PRs
renv
Rmd vignette #398One problem I see with
v0.5.0
is that it produces a new warning in the console when a report is downloaded (which I'm not sure we have any control over):Thoughts? We could go back to
v0.3.0
I suppose to avoid it?