Bump to 0.2.5

statnmap · statnmap · commit d5c3aa48f1f4 · 2022-05-15T13:43:28.000+02:00
- Update Readme and NEWS
diff --git a/DESCRIPTION b/DESCRIPTION
@@ -1,6 +1,6 @@
 Package: attachment
 Title: Deal with Dependencies
-Version: 0.2.4.9001
+Version: 0.2.5
 Authors@R:
     c(person(given = "Sébastien",
              family = "Rochette",
diff --git a/NEWS.md b/NEWS.md
@@ -1,4 +1,4 @@
-# attachment 0.2.4.900x
+# attachment 0.2.5
 ## Major changes
 
 * add `create_renv_for_dev()` and `create_renv_for_prod()` function to create `renv.lock` file based on development project (@VincentGuyader and @statnmap).
diff --git a/R/att_from_rmds.R b/R/att_from_rmds.R
@@ -60,7 +60,13 @@ att_from_rmd <- function(path, temp_dir = tempdir(), warn = -1,
   yaml <- c("\n# yaml to parse \n",
             paste(yaml_pkg, "\n"))
   cat(yaml, file = r_file, append = TRUE)
-  att_from_rscript(r_file)
+  res <- att_from_rscript(r_file)
+
+  # clean tempdir
+  file.remove(runR)
+  file.remove(r_file)
+
+  return(res)
 }
 
 #' Get all packages called in vignettes folder
diff --git a/README.Rmd b/README.Rmd
@@ -108,20 +108,27 @@ for (i in to_install) {
 }
 ```
 
-### For bookdown
+### For bookdown, pagedown, quarto
 
-If you write a {bookdown} and want to publish it on Github using Travis for instance, you will need a DESCRIPTION file with list of dependencies just like for a package. In this case, you can use the function to description from import/suggest: `att_to_desc_from_is()`.
+If you write a {bookdown} and want to publish it on Github using GitHub Actions or GitLab CI for instance, you will need a DESCRIPTION file with list of dependencies just like for a package. In this case, you can use the function to description from import/suggest: `att_to_desc_from_is()`.
 
 ```{r, eval=FALSE}
+usethis::use_description()
 # bookdown Imports are in Rmds
 imports <- c("bookdown", attachment::att_from_rmds("."))
 attachment::att_to_desc_from_is(path.d = "DESCRIPTION",
                                 imports = imports, suggests = NULL)
 ```
 
+Then, install dependencies with
+```{r, eval=FALSE}
+remotes::install_deps()
+```
+
 
 ### To list information
-Of course, you can also use {attachment} out of a package to list all package dependencies of R scripts using `att_from_rscripts()` or Rmd files using `att_from_rmds()`.  
+
+Of course, you can also use {attachment} out of a package to list all package dependencies of R scripts using `att_from_rscripts()` or Rmd/qmd files using `att_from_rmds()`.  
 If you are running this inside a Rmd, you may need parameter `inside_rmd = TRUE`.  
 
 ```{r, eval=TRUE}
@@ -131,17 +138,18 @@ att_from_rscripts(path = dummypackage)
 att_from_rmds(path = file.path(dummypackage, "vignettes"), inside_rmd = TRUE)
 ```
 
-## Vignette
+## Vignettes
 
-Package {attachment} has a vignette to present the different functions available. There is also a recommendation to have a `dev_history.R` in the root directory of your package. (*Have a look at [dev_history.R](https://github.com/ThinkR-open/attachment/blob/main/dev/dev_history.R) in the present package*)
+Package {attachment} has vignettes to present the different functions available. There is also a recommendation to have a `dev_history.R` in the root directory of your package. (*Have a look at [dev_history.R](https://github.com/ThinkR-open/attachment/blob/main/dev/dev_history.R) in the present package*)
 
 ```{r, eval=FALSE}
-vignette("fill-pkg-description", package = "attachment")
+vignette("a-fill-pkg-description", package = "attachment")
+vignette("b-bookdown-and-scripts", package = "attachment")
+vignette("use_renv", package = "attachment")
 ```
 
-The vignette is available on the {pkgdown} page: <https://thinkr-open.github.io/attachment/articles/fill-pkg-description.html>
+The vignettes are available on the {pkgdown} page, in the "Articles" menu: <https://thinkr-open.github.io/attachment/>
 
-See full documentation realized using {pkgdown} at <https://thinkr-open.github.io/attachment/>  
   
 ## Code of Conduct
 
diff --git a/README.md b/README.md
@@ -85,13 +85,13 @@ dummypackage <- file.path(tmpdir, "dummypackage")
 # browseURL(dummypackage)
 att_amend_desc(path = dummypackage, inside_rmd = TRUE)
 #> Updating dummypackage documentation
-#> Updating roxygen version in /tmp/RtmpdAJaCu/dummypackage/DESCRIPTION
+#> Updating roxygen version in /tmp/RtmpK2L9Ud/dummypackage/DESCRIPTION
 #> ℹ Loading dummypackage
 #> Writing NAMESPACE
 #> Writing NAMESPACE
 #> Package(s) Rcpp is(are) in category 'LinkingTo'. Check your Description file to be sure it is really what you want.
 #> [-] 1 package(s) removed: utils.
-#> [+] 2 package(s) added: stats, ggplot2.
+#> [+] 2 package(s) added: stats, glue.
 ```
 
 ### For installation
@@ -130,24 +130,32 @@ for (i in to_install) {
 }
 ```
 
-### For bookdown
+### For bookdown, pagedown, quarto
 
-If you write a {bookdown} and want to publish it on Github using Travis
-for instance, you will need a DESCRIPTION file with list of dependencies
-just like for a package. In this case, you can use the function to
-description from import/suggest: `att_to_desc_from_is()`.
+If you write a {bookdown} and want to publish it on Github using GitHub
+Actions or GitLab CI for instance, you will need a DESCRIPTION file with
+list of dependencies just like for a package. In this case, you can use
+the function to description from import/suggest:
+`att_to_desc_from_is()`.
 
 ``` r
+usethis::use_description()
 # bookdown Imports are in Rmds
 imports <- c("bookdown", attachment::att_from_rmds("."))
 attachment::att_to_desc_from_is(path.d = "DESCRIPTION",
                                 imports = imports, suggests = NULL)
 ```
 
+Then, install dependencies with
+
+``` r
+remotes::install_deps()
+```
+
 ### To list information
 
 Of course, you can also use {attachment} out of a package to list all
-package dependencies of R scripts using `att_from_rscripts()` or Rmd
+package dependencies of R scripts using `att_from_rscripts()` or Rmd/qmd
 files using `att_from_rmds()`.  
 If you are running this inside a Rmd, you may need parameter
 `inside_rmd = TRUE`.
@@ -158,26 +166,25 @@ dummypackage <- system.file("dummypackage", package = "attachment")
 att_from_rscripts(path = dummypackage)
 #> [1] "stats"        "testthat"     "dummypackage"
 att_from_rmds(path = file.path(dummypackage, "vignettes"), inside_rmd = TRUE)
-#> [1] "knitr"     "rmarkdown" "ggplot2"
+#> [1] "knitr"     "rmarkdown" "glue"
 ```
 
-## Vignette
+## Vignettes
 
-Package {attachment} has a vignette to present the different functions
+Package {attachment} has vignettes to present the different functions
 available. There is also a recommendation to have a `dev_history.R` in
 the root directory of your package. (*Have a look at
-[dev\_history.R](https://github.com/ThinkR-open/attachment/blob/main/dev/dev_history.R)
+[dev_history.R](https://github.com/ThinkR-open/attachment/blob/main/dev/dev_history.R)
 in the present package*)
 
 ``` r
-vignette("fill-pkg-description", package = "attachment")
+vignette("a-fill-pkg-description", package = "attachment")
+vignette("b-bookdown-and-scripts", package = "attachment")
+vignette("use_renv", package = "attachment")
 ```
 
-The vignette is available on the {pkgdown} page:
-<https://thinkr-open.github.io/attachment/articles/fill-pkg-description.html>
-
-See full documentation realized using {pkgdown} at
-<https://thinkr-open.github.io/attachment/>
+The vignettes are available on the {pkgdown} page, in the “Articles”
+menu: <https://thinkr-open.github.io/attachment/>
 
 ## Code of Conduct
 
diff --git a/dev/dev_history.R b/dev/dev_history.R
@@ -111,7 +111,8 @@ rcmdcheck::rcmdcheck(args = c("--no-manual", "--as-cran"))
 
 # Check content
 # remotes::install_github("ThinkR-open/checkhelper")
-checkhelper::find_missing_tags()
+out <- checkhelper::find_missing_tags()
+View(out)
 
 # Check spelling
 # usethis::use_spell_check()
@@ -137,6 +138,7 @@ aa
 # _win devel
 devtools::check_win_devel()
 devtools::check_win_release()
+devtools::check_mac_release()
 
 # Check reverse dependencies
 # remotes::install_github("r-lib/revdepcheck")
@@ -146,14 +148,17 @@ usethis::use_build_ignore("revdep/")
 devtools::revdep()
 library(revdepcheck)
 # In another session
+revdepcheck::revdep_todo()
+# revdepcheck::revdep_add(packages = "fusen")
 id <- rstudioapi::terminalExecute("Rscript -e 'revdepcheck::revdep_check(num_workers = 4)'")
 rstudioapi::terminalKill(id)
 # See outputs
-revdep_details(revdep = "pkg")
-revdep_summary()                 # table of results by package
+revdep_details(revdep = "fusen")
+revdep_summary()
+# table of results by package
 revdep_report() # in revdep/
 # Clean up when on CRAN
-revdep_reset()
+revdepcheck::revdep_reset()
 
 # Update NEWS
 # Bump version manually and add list of changes

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-# attachment 0.2.4.900x`
	`1`	`+# attachment 0.2.5`
`2`	`2`	`## Major changes`
`3`	`3`
`4`	`4`	* add `create_renv_for_dev()` and `create_renv_for_prod()` function to create `renv.lock` file based on development project (@VincentGuyader and @statnmap).