Skip to content

Conversation

JordanLongstaff
Copy link
Contributor

Nullable Booleans are possible, and must go through value checks just like nonnull Booleans. While it's tempting to reach for the elvis operator (?:), the equality operator is preferred.

This is the inspiration behind allowing the Boolean matchers to have nullable receivers. For testing purposes, it's simply more convenient.

@JordanLongstaff JordanLongstaff requested a review from a team as a code owner March 14, 2025 03:41
@sksamuel sksamuel enabled auto-merge March 29, 2025 20:16
@sksamuel sksamuel added this pull request to the merge queue Mar 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Mar 29, 2025
@sksamuel sksamuel added this pull request to the merge queue Mar 30, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 30, 2025
@sksamuel sksamuel added this pull request to the merge queue Mar 30, 2025
Merged via the queue into kotest:master with commit b9cd3b7 Mar 30, 2025
12 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants