One aim of our open-source packages at ThinkR is to make our development workflows easier. {attachment} and {fusen} are developed maintained to help packages development and maintenance. Inception… If they help us every day, they can probably help you as well! In this blog post, I present the lastest changes of these two packages. If you want to know how ...

{fusen} gets some maturity! v0.3 is a big rebranding for a more fluid experience, from beginners to advanced developers. Creating a fully documented and tested package has never been so easy and enjoyable. Experience “Rmd first” to the fullest. At first, I imagined {fusen} to help beginners start building R packages. Following the ‘Rmd first’ method, I am convinced that ...

A new version of {attachment} is available on CRAN. Get dependencies installed from GitHub, GitLab, … and add the link to the ‘Remotes’ field in the DESCRIPTION file of your package. install.packages(“attachment”) While waiting for CRAN release, you can install from GitHub: remotes::install_github(“ThinkR-open/[email protected]”) {attachment} helps you deal with dependencies during your package development. All packages used in your code needs ...

It is with great pleasure that we can announce that the paper version of the book “Engineering Production-Grade Shiny Apps” is available. It is published in the R Series by Chapman & Hall. If you want to use shiny with rigour , and use this techno to push your applications into production, this book is for you. The ThinkR team ...

You regularly create projects on GitLab with a common skeleton, you want to retrieve the list of GitLab issues to create a report, you are looking for batch modifications of your projects? Use the GitLab API from your preferred programming language R. Communicate with GitLab API from R Here is a small example as issued from the {gitlabr} Readme on ...

With first version of {fusen} 0.2.4 now available on CRAN, you do not have any excuses not to try it in your daily workflows. install.packages(“fusen”) Add new documented and tested functionalities in an existing package If you already develop packages, {fusen} is for you. Developing a package requires to write some code and examples in multiple places: “R/”, “tests/”, “vignettes/”. ...

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 ...

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 ...

You know how to build a Rmardown, you were told or would like to put your work in a R package, but you think this is too much work? You do not understand where to put what and when? What if writing a Rmd was the same as writing a package? Follow the “Rmd-first” method and let {fusen} guide you ...

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 ...

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 ...

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 ...

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. ...

A little blog post about where to look if you want to get started with {golem}, and an invitation to code with us in October. ...

We are pleased to announce that our package {attachment} is now available on CRAN. The goal of attachment is to help to deal with package dependencies during package development. It also gives useful tools to install or list missing packages used inside Rscripts or Rmds. Deal with dependencies during package development If you ever had the following error when checking ...

Shiny App as a Package In a previous post, I’ve introduced the {golem} package, which is an opinionated framework for building production-ready Shiny Applications. This framework starts by creating a package skeleton waiting to be filled. But, in a world where Shiny Applications are mostly created as a series of files, why bother with a package? This is the question ...