From 36ec45e4be1c2137864e80dcdc4317ff72621c79 Mon Sep 17 00:00:00 2001 From: MikeJohnPage <38110953+MikeJohnPage@users.noreply.github.com> Date: Thu, 14 Dec 2023 22:54:21 +0100 Subject: [PATCH] Update lifecycle.Rmd (#1038) * Update lifecycle.Rmd * Update lifecycle.Rmd Co-authored-by: Jennifer (Jenny) Bryan * Update lifecycle.Rmd Remove footnote --------- Co-authored-by: Jennifer (Jenny) Bryan --- lifecycle.Rmd | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/lifecycle.Rmd b/lifecycle.Rmd index 5e607bdbc..4d6c702da 100644 --- a/lifecycle.Rmd +++ b/lifecycle.Rmd @@ -96,11 +96,9 @@ These three different views of usethis's evolution are all useful for different Formally, an R package version is a sequence of at least two integers separated by either `.` or `-`. For example, `1.0` and `0.9.1-10` are valid versions, but `1` and `1.0-devel` are not. -Base R offers the `utils::package_version()`[^lifecycle-2] function to parse a package version string into a proper S3 class by the same name. +Base R offers the `package_version()` function to parse a package version string into a proper S3 class by the same name. This class makes it easier to do things like compare versions. -[^lifecycle-2]: We can call `package_version()` directly here, but in package code, you should use the `utils::package_version()` form and list the utils package in `Imports`. - ```{r} #| error: true package_version(c("1.0", "0.9.1-10"))