Skip to content

Commit 3ec8266

Browse files
authored
Highlight the Cucumber core changes in v5 upgrade guide
1 parent 5e2f311 commit 3ec8266

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

docs/upgrade_v5.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,17 @@ If you are using Cucumber Scala 4.7.x and want to upgrade to 5.x, please note th
55
Starting from version 5.x, Cucumber Scala will try to be as close as possible to the Cucumber Java implementation while remaining Scala oriented.
66
This means that package names, parameters order, internal code... will be more consistent with the Java implementation.
77

8-
See also the [CHANGELOG](https://github.com/cucumber/cucumber-jvm/blob/master/CHANGELOG.md) from Cucumber Core.
8+
## Cucumber Core changes
9+
10+
Please read the [CHANGELOG](https://github.com/cucumber/cucumber-jvm/blob/master/CHANGELOG.md) from Cucumber Core.
11+
12+
### Empty values in Datatables
13+
14+
Starting with Cucumber 5.x, empty values in Datatables are now represented as `null` instead of an empty string previously.
15+
16+
Check out the [Empty values section in Transformers documentation](https://github.com/cucumber/cucumber-jvm-scala/blob/master/docs/transformers.md#empty-values) to learn how to have empty values in your Datatables.
17+
18+
You can also consider [upgrading to Cucumber Scala 6.x](upgrade_v6.md) straight away as Cucumber Scala 6.x provides a way to map Datatables as collections of `Option`s so that you don't have to deal with `null` anyway.
919

1020
## Packages
1121

0 commit comments

Comments
 (0)