-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Do not raise when variable is defined #921
Conversation
Variables which are defined but have a nil value should not raise. See #749
Can you fix the style violations? |
Fixed the ones that I introduced. The others should be fixed in another PR, I guess. |
ugh sorry, I wasn't aware that things are failing on master too |
Hm it's not failing for me locally. Not sure why it's failing on travis. |
.rubocop.yml
Outdated
@@ -73,9 +73,6 @@ Style/Documentation: | |||
Style/ClassAndModuleChildren: | |||
Enabled: false | |||
|
|||
Style/TrailingComma: | |||
Enabled: false |
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.
The style violations in existing code are because of this change to the rubocop style, which shouldn't be needed for this PR.
This reverts commit cdf1ce9.
Hmm, picked up other rubycop with me, fixed. |
@dylanahsmith @fw42 thanks, that was rather fast from PR to acceptance 😄 |
Variables which are defined but have a nil value should not raise.
See #749