Skip to content

Commit f1f7195

Browse files
committed
Polish NEWS
1 parent 9b075e8 commit f1f7195

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

NEWS.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
# dplyr (development version)
22

3-
* The `rows_*()` functions now always retain the column types of `x`. This
4-
behavior was documented, but previously wasn't being applied correctly
5-
(#6240).
6-
3+
* The `rows_*()` functions no longer require that the key values in `x` uniquely
4+
identify each row. Additionally, `rows_insert()` and `rows_delete()` no
5+
longer require that the key values in `y` uniquely identify each row. Relaxing
6+
this restriction should make these functions more practically useful for
7+
data frames, and alternative backends can enforce this in other ways as needed
8+
(i.e. through primary keys) (#5553).
9+
710
* `rows_insert()` gained a new `conflict` argument allowing you greater control
811
over rows in `y` with keys that conflict with keys in `x`. A conflict arises
912
if a key in `y` already exists in `x`. By default, a conflict results in an
@@ -15,21 +18,18 @@
1518
argument allowing you greater control over rows in `y` with keys that are
1619
unmatched by the keys in `x`. By default, an unmatched key results in an
1720
error, but you can now also `"ignore"` these `y` rows (#5984, #5699).
18-
19-
* The `rows_*()` functions no longer require that the key values in `x` uniquely
20-
identify each row. Additionally, `rows_insert()` and `rows_delete()` no
21-
longer require that the key values in `y` uniquely identify each row. Relaxing
22-
this restriction should make these functions more practically useful for
23-
data frames, and alternative backends can enforce this in other ways as needed
24-
(i.e. through primary keys) (#5553).
2521

26-
* The `rows_*()` functions now fail elegantly if `y` is a zero column data frame
27-
and `by` isn't specified (#6179).
28-
2922
* `rows_delete()` no longer requires that the columns of `y` be a strict subset
3023
of `x`. Only the columns specified through `by` will be utilized from `y`,
3124
all others will be dropped with a message.
3225

26+
* The `rows_*()` functions now always retain the column types of `x`. This
27+
behavior was documented, but previously wasn't being applied correctly
28+
(#6240).
29+
30+
* The `rows_*()` functions now fail elegantly if `y` is a zero column data frame
31+
and `by` isn't specified (#6179).
32+
3333
# dplyr 1.0.8
3434

3535
* Better display of error messages thanks to rlang 1.0.0.

0 commit comments

Comments
 (0)