• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

bombsimon / wsl / 139
89%
main: 92%

Build:
Build:
LAST BUILD BRANCH: lock-unlock
DEFAULT BRANCH: main
Ran 10 Nov 2019 01:25PM UTC
Jobs 3
Files 2
Run time 51s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

10 Nov 2019 01:22PM UTC coverage: 89.1%. Remained the same
139

push

travis-ci-com

bombsimon
Only force when to add (not remove) case trailing whitespace

This commit loosens up quite alot on how case blocks should look. The main
reason is because they're quite complex, especially if you consider
comments. A comment in the end of a case might (depending on ths Pos())
belong to the next case for example. Even gofmt handles indentation
for comments in case blocks in multiple ways.

From now on the end user may or may not end cases with newlines or
comments. With this commit a user can configure when you *must* end
with a whitespace to improve readability which essentially is what this
litner is about

11 of 11 new or added lines in 1 file covered. (100.0%)

1128 of 1266 relevant lines covered (89.1%)

378.45 hits per line

Jobs
ID Job ID Ran Files Coverage
1 139.1 10 Nov 2019 01:25PM UTC 0
89.1
Travis Job 139.1
2 139.2 10 Nov 2019 01:26PM UTC 0
89.1
Travis Job 139.2
3 139.3 10 Nov 2019 01:26PM UTC 0
89.1
Travis Job 139.3
Source Files on build 139
Detailed source file information is not available for this build.
  • Back to Repo
  • Build #139
  • 5adde1b1 on github
  • Prev Build on case-trailing-newline (#141)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc