Bigtable: clean up redundant code#5286
Merged
chingor13 merged 2 commits intogoogleapis:masterfrom Jul 30, 2019
Merged
Conversation
googlebot
added
the
cla: yes
Contributor
|
@liubonan, can you please run |
igorbernstein2
left a comment
igorbernstein2
left a comment
There was a problem hiding this comment.
LGTM, but please run the formatter
Codecov Report
@@ Coverage Diff @@
## master #5286 +/- ##
============================================
+ Coverage 50.47% 50.48% +<.01%
Complexity 23875 23875
============================================
Files 2258 2258
Lines 227482 227482
Branches 24978 24978
============================================
+ Hits 114828 114834 +6
+ Misses 104035 104029 -6
Partials 8619 8619
Continue to review full report at Codecov.
|
chingor13
approved these changes
Jul 30, 2019
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
6 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.
Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for context and/or discussion)