fix: satisfy safe-navigation lint - #10
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
empty?conditional with an equivalent explicit nil guardLint/SafeNavigationWithEmptyVerification
bundle exec rubocop lib/fizzy/cli/base.rb— 1 file, no offensesbundle exec rake— 114 runs, 262 assertions, 0 failures, 0 errors; 39 files, no RuboCop offensesgit diff --checkThis is a prerequisite for the separate
Gemfile.lockcleanup PR #9, whose CI currently resolves RuboCop 1.88.2 and exposes this pre-existing warning.