diff --git a/DESCRIPTION b/DESCRIPTION index 422c0f7..2e9bf5a 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -1,6 +1,6 @@ Package: versus Title: Compare Data Frames -Version: 0.3.0.9000 +Version: 0.3.1.9000 Authors@R: c( person("Ryan", "Dickerson", , "fresh.tent5866@fastmail.com", role = c("aut", "cre", "cph")), person("Eli", "Pousson", , "eli.pousson@gmail.com", role = "ctb", diff --git a/NEWS.md b/NEWS.md index 8f55e82..d26e5e1 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,5 +1,7 @@ # versus (development version) +# versus 0.3.1 + * New `table_id` argument in `compare()` allows custom table identifiers. By default, outputs identify tables as "a" and "b". You can now provide meaningful names e.g. `compare(..., table_id = c("original", "updated"))`, which diff --git a/README.md b/README.md index f8acc00..be447c6 100644 --- a/README.md +++ b/README.md @@ -66,10 +66,10 @@ Use `compare()` to create a comparison of two tables. A comparison contains: -- `compare()$intersection`: columns in both tables and rows with - differing values -- `compare()$unmatched_cols`: columns in only one table -- `compare()$unmatched_rows`: rows in only one table +- `compare()$intersection`: columns in both tables and rows with + differing values +- `compare()$unmatched_cols`: columns in only one table +- `compare()$unmatched_rows`: rows in only one table ``` r comparison <- compare(example_df_a, example_df_b, by = car) diff --git a/cran-comments.md b/cran-comments.md index 0037a2f..a1ed5ee 100644 --- a/cran-comments.md +++ b/cran-comments.md @@ -1,3 +1,17 @@ +## Test environments + +* local macOS 14.4.1, R 4.5.1 +* win-builder (devel) + ## R CMD check results -0 errors | 0 warnings | 0 notes +0 errors | 0 warnings | 1 note (local) / 1 note (win-builder) + +* Local macOS: `checking for future file timestamps ... NOTE` + unable to verify current time (expected in sandboxed CI environment) +* Win-builder (devel): `checking CRAN incoming feasibility ... NOTE` + Version contains large components (0.3.0.9000) — expected when checking dev builds + +## Additional comments + +* Current CRAN check results for 0.3.0 show a NOTE about the non-API call `STRING_PTR` in compiled code. The package no longer includes compiled code, so this NOTE should disappear with 0.3.1.