Antoine Fabri
Antoine Fabri
So we can modifiy README in time https://github.com/rstudio/rstudio/issues/13177
So we don't have to edit DESCRIPTION and .Rproj
on Mattermost In particular check how it plays out with pkgdown If packagedown doesn't remove the files provide a wrapper that does remove them
I'm not sure about this dcf strategy because it implies : * potential duplication of code (if user has checking code in package already) * checking code that is not...
Other things that I often wonder about options and environment values are : * What are their default values ? * What are the values that we've set in .RProfile...
Since those are stable. It's a manual chore but that's useful. They're documented (at least some/most) in `?options` We need a mechanism for this too.
Discussed today with @krlmlr * Git in theory should relieve us from the anxiety of creating a mess, because we can always go back * In practice however it's common...
Closes #456 So we can suggest rather than import
``` r constructive::construct(data.frame(a=1, a =2, check.names = FALSE)) #> {constructive} couldn't create code that reproduces perfectly the input #> ℹ Call `construct_issues()` to inspect the last issues #> data.frame(a =...
``` r x {constructive} couldn't create code that reproduces perfectly the input #> ℹ Call `construct_issues()` to inspect the last issues #> as.POSIXct("2024-07-22 13:25:22.86897", tz = "UTC") ``` ``` r...