feat: add reportIfNil
to report unexpected nil values
#165
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
reportIfNil
: Report unexpectednil
values as issuesThis PR introduces a new utility,
reportIfNil
, to theswift-issue-reporting
library. It evaluates an optional value and reports an issue if the value isnil
, using the existingIssueReporter
infrastructure.Motivation
While
withErrorReporting
handles thrown errors, there is currently no equivalent for reporting unexpectednil
values — a common source of bugs in Swift.Tests Included
Tests are split into focused cases for better clarity and maintainability:
nil
value with default messagenil
value with custom messagenil
Related
Complements existing
withErrorReporting
functionality by offering a similar utility for handling optional values that shouldn't benil
.