Skip to content
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

Partial Fix for #83 (Excluding Gocyclo) #84

Merged
merged 15 commits into from
Jan 24, 2019
Merged

Partial Fix for #83 (Excluding Gocyclo) #84

merged 15 commits into from
Jan 24, 2019

Conversation

nilathedragon
Copy link
Contributor

I fixed the errors except for gocyclo. Its an A+ grade now

@coveralls
Copy link

coveralls commented Jan 22, 2019

Pull Request Test Coverage Report for Build 596

  • 5 of 7 (71.43%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.05%) to 89.238%

Changes Missing Coverage Covered Lines Changed/Added Lines %
widgets/linechart/axes/label.go 1 3 33.33%
Totals Coverage Status
Change from base Build 585: -0.05%
Covered Lines: 3947
Relevant Lines: 4423

💛 - Coveralls

Copy link
Owner

@mum4k mum4k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the help with these issues. I have added a couple of suggestions below.

As for the Gocyclo issues - I have reviewed them and believe that we are fine ignoring those for now. Most of them are in the tests.

eventqueue/eventqueue_test.go Outdated Show resolved Hide resolved
widgets/linechart/axes/label.go Outdated Show resolved Hide resolved
@@ -39,6 +39,19 @@ var lineStyleChars = map[LineStyle]map[linePart]rune{
vAndRight: '├',
vAndH: '┼',
},
LineStyleDouble: {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, thanks a lot!

Would you mind sending this in a separate pull request? A couple of reasons really:

  1. this being a new feature - I would prefer to merge it into the devel branch instead of the master and follow a release cycle.
  2. for the posterity - the pull request history or rollbacks become much cleaner when each pull request is focused on only one bug / feature / etc.
  3. we could iterate on this change a bit more without blocking your original PR regarding the lint issues. This new feature (new line style) could benefit from some test coverage. An advice I got a long time ago was to accompany each code change with at least minimal corresponding change in tests to "capture" the new feature in a working state.

I have no more comments on this PR without the new line style, so once we remove the line style from this scope - this is ready to go.

For (3) we could expand the test cases inside the border_test:

https://github.com/mum4k/termdash/blob/master/draw/border_test.go

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've reverted the merge with the line-style.

I'll check out that test file 👍

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

This reverts commit 93423a8, reversing
changes made to 02bb0d1.
@mum4k mum4k merged commit 1e1dc15 into mum4k:master Jan 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants