From 8705a3437fa7f973c8cd30dea2b602e0e7ec5b8d Mon Sep 17 00:00:00 2001
From: Indrajeet Patil <patilindrajeet.science@gmail.com>
Date: Sun, 29 Sep 2024 21:22:53 +0200
Subject: [PATCH] also include checklist

---
 paper/paper.Rmd |  2 +-
 paper/paper.bib | 10 ++++++++++
 paper/paper.md  |  5 +++--
 3 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/paper/paper.Rmd b/paper/paper.Rmd
index 4f3d31a09..dc2b97864 100644
--- a/paper/paper.Rmd
+++ b/paper/paper.Rmd
@@ -219,7 +219,7 @@ There are two main ways to customize it:
 
   - Create new linters (by leveraging functions like `lintr::make_linter_from_xpath()`) tailored to match project- or organization-specific coding standards.
 
-Indeed, `{goodpractice}` [@Padgham2024] bundles a set of custom linters that are not part of the default set of `{lintr}` linters, while `{flint}` [@Bacher2024] provides a way to fix the lints detected by `{lintr}`. Moreover, `{box.linters}` [@Basa2024] extends `{lintr}` to support `{box}` modules [@Rudolph2024].
+Indeed, `{goodpractice}` [@Padgham2024] bundles a set of custom linters that are not part of the default set of `{lintr}` linters, while `{flint}` [@Bacher2024] provides a way to fix the lints detected by `{lintr}`. Moreover, `{box.linters}` [@Basa2024] extends `{lintr}` to support `{box}` modules [@Rudolph2024], while `{checklist}` includes linters as one of the strict checks for R packages [@Onkelinx2024].
 
 # Benefits of using `{lintr}`
 
diff --git a/paper/paper.bib b/paper/paper.bib
index 278bde85a..329f7c403 100644
--- a/paper/paper.bib
+++ b/paper/paper.bib
@@ -105,3 +105,13 @@ @Manual{Wickham2024roxy
     note = {R package version 7.3.2},
     url = {https://CRAN.R-project.org/package=roxygen2},
   }
+
+@Manual{Onkelinx2024,
+    title = {checklist: A Thorough and Strict Set of Checks for {R} Packages and Source Code. Version 0.4.0},
+    author = {Thierry Onkelinx},
+    year = {2024},
+    url = {https://inbo.github.io/checklist/},
+    abstract = {An opinionated set of rules for R packages and R source code projects.},
+    keywords = {quality control; documentation; publication},
+    doi = {10.5281/zenodo.4028303},
+  }
diff --git a/paper/paper.md b/paper/paper.md
index 0f0123fe3..7e90bf7c8 100644
--- a/paper/paper.md
+++ b/paper/paper.md
@@ -1,6 +1,6 @@
 ---
 title: "Static Code Analysis for R"
-date: "2024-09-28"
+date: "2024-09-29"
 tags: ["R", "linter", "tidyverse"]
 authors:
   - name: Jim Hester
@@ -298,7 +298,8 @@ Indeed, `{goodpractice}` [@Padgham2024] bundles a set of custom linters
 that are not part of the default set of `{lintr}` linters, while
 `{flint}` [@Bacher2024] provides a way to fix the lints detected by
 `{lintr}`. Moreover, `{box.linters}` [@Basa2024] extends `{lintr}` to
-support `{box}` modules [@Rudolph2024].
+support `{box}` modules [@Rudolph2024], while `{checklist}` includes
+linters as one of the strict checks for R packages [@Onkelinx2024].
 
 # Benefits of using `{lintr}`