Avoid a nil result #246
Open
Avoid a nil result #246
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This prevents throwing our stack just because the `result` is `nil`.
julienXX
reviewed
Mar 28, 2018
| # notify_result('I do not like pie', {'reply' => true}) #=> 'I do not like pie' | ||
| # notify_result('@timeout', {'reply' => true}) #=> '@timeout' | ||
| # notify_result('I may like pie', {}) #=> :i_may_like_pie | ||
| def notify_result(result, options, always_string = false) |
Owner
There was a problem hiding this comment.
How about giving a default value to result instead?
|
@ryanfaerman Are you still interested in this PR? I encountered this issue too, and want to fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This prevents throwing our stack just because the
resultisnil.