-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Catch errors in the code inside the must
check
#105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good style! I’ve added two comments, let me know what you think.
@@ -0,0 +1,14 @@ | |||
# frozen_string_literal: true | |||
|
|||
class ExpectedFallInMustWhenTypeIsFirstAdvanced < Actor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this class be named ExpectedFailInMustWhenTypeIsFirstAdvanced?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done: 1b08616
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add an entry to the CHANGELOG, under unreleased
? 🙏🏻
Done |
must
must
check
To simplify the code inside the lambda by getting rid of methods such as
.to_i
.