2021-05-31 / Colin Fay / golem, shiny

About {golem} 0.3.1

The new version of {golem} (0.3.1) has been available on CRAN 🎉 for about a month now. This new version includes a lot of new things, but we notably focused on working on two important new features: allowing you to extend {golem} via templates, and supporting for the latest changes in {shiny}. Extending {golem} One of the challenges when it ...

Processus development collaborative

2021-04-19 / Sébastien Rochette / development, Rmarkdown, rstudio, tips

A guide to collaborative development with R for reproducible PROPRE reporting

With our “PROPRE” Project Guide, get a publishing committee and a development team to collaborate on creating your automated reports using the “PROPRE” methodology. Follow our suggestions for organization, tools and R development practices, for a controlled and benevolent DevOps practice. It is possible to collaborate around git in a team composed of developers and non developers. In this guide ...

2021-01-19 / Sébastien Rochette / development, package

{attachment} v0.2.0 : find dependencies in your scripts and fill package DESCRIPTION

New version of {attachment} has been published on CRAN ! We continue to improve its functionalities to help you deal with dependencies in R, in particular during package development. Since our last blog post presenting the aim of {attachment}, two versions reached CRAN. The full documentation is available on the {pkgdown} website : https://thinkr-open.github.io/attachment. Still, for package developers, att_amend_desc() keeps ...

devindocker package logo for development in docker container

2020-11-07 / Sébastien Rochette / development, docker, package, rstudio

How to develop inside a Docker container to ease collaboration?

To ensure the reproducibility of your projects, you can develop in the Docker container that you will use to share your work. Indeed, what to do when your data analyses, publications, models are used by users with different versions of operating systems and R packages R? How do you ensure that your Dockerfile delivered with your package or project is ...

A HTML report created from git messages using gitdown package

2020-08-10 / Sébastien Rochette / tips, development, package

Download Gitlab or Github issues and make a summary report of your commits

While working on our {gitdown} package, I wanted to show more information on the report generated by retrieving all issues of my Gitlab / Github repositories. Indeed, titles of issues could improve readability and information of the git report of this package. How can I download all issues information from git repositories? Context of {gitdown} development {gitdown} is a package ...

Transform a directory of flles to gitlab or github, using git

2020-08-10 / Sébastien Rochette / development, git

Transform a folder as git project synchronized on Github or Gitlab

You have been working for years on your R scripts, and saved all versions as “script_v1.R”, “script_v2.R”, “script_v2_best-of-the-world.R”, … One day, you heard about git, a versioning system that allows you to make your files travel through time. But, how to transform a directory of falsely versioned files into a git repository and synchronize it online? Originally, I wanted to ...

2020-06-10 / Colin Fay / golem, learning, shiny

What’s a “successful” Shiny Application?

One of the things that we keep promoting in the ThinkR team are good practices for production software engineering in R. Of course, that implies Shiny Applications—and even more if we introduce the {golem} package, which promotes good practices for “production-grade” Shiny application. But let’s take a step back and think about what makes a successful/production-grade Shiny Application. ...