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

Teamwork / kommentaar
53%
master: 54%

Build:
Build:
LAST BUILD BRANCH: refs/tags/v0.3.2
DEFAULT BRANCH: master
Repo Added 17 Jan 2024 02:00PM UTC
Token Hl0IHChx7sdBtong96gTfQfrlaivub8Ak regen
Build 82 Last
Files 10
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

LAST BUILD ON BRANCH fix/cross-package-enum
branch: fix/cross-package-enum
CHANGE BRANCH
x
Reset
Sync Branches
  • fix/cross-package-enum
  • docker
  • enhancement/better-generic-support
  • enhancement/generic-types-map
  • enhancement/preinstall-kommentaar-docker
  • enums
  • feature/update-go-1.26
  • fix-embed-json-dash
  • fix/atomic-output-write
  • fix/generics
  • fix/generics-support
  • fix/linter
  • fix/maptype-resolve-selectors-and-slices
  • fix/package-name-collision
  • generics
  • go-compiler
  • infer-required
  • log-empty-tags
  • map-of-slice-additional-properties
  • maps
  • master
  • refs/tags/v0.1.10
  • refs/tags/v0.1.11
  • refs/tags/v0.1.9
  • refs/tags/v0.2.0
  • refs/tags/v0.2.1
  • refs/tags/v0.2.2
  • refs/tags/v0.2.3
  • refs/tags/v0.2.4
  • refs/tags/v0.2.5
  • refs/tags/v0.2.6
  • refs/tags/v0.2.7
  • refs/tags/v0.2.8
  • refs/tags/v0.3.0
  • refs/tags/v0.3.1
  • refs/tags/v0.3.2
  • run-output-opt

23 Apr 2026 05:01PM UTC coverage: 53.278% (+0.3%) from 52.998%
24848043446

Pull #110

github

shane-tw
Fix enum variations not resolved for cross-package enum types

When a field annotated with {enum} has a type from another package
(e.g. `pkg.SomeType`), getEnumVariations was never called with the
correct type name. The SelectorExpr branch called canonicalType which
resolved the type to its underlying primitive and then jumped back via
goto start; the re-entry then called getEnumVariations with the
primitive name ("string") rather than the original type name
("SomeType"), so no constants were ever matched.

Fix: call getEnumVariations with the original pkg and type name before
executing goto start in the SelectorExpr branch, mirroring what the
Ident branch already does.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pull Request #110: Fix enum variations not resolved for cross-package enum types

13 of 18 new or added lines in 1 file covered. (72.22%)

1 existing line in 1 file now uncovered.

1162 of 2181 relevant lines covered (53.28%)

45.51 hits per line

Relevant lines Covered
Build:
Build:
2181 RELEVANT LINES 1162 COVERED LINES
45.51 HITS PER LINE
Source Files on fix/cross-package-enum
  • Tree
  • List 10
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
24848043446 fix/cross-package-enum Fix enum variations not resolved for cross-package enum types When a field annotated with {enum} has a type from another package (e.g. `pkg.SomeType`), getEnumVariations was never called with the correct type name. The SelectorExpr branch called ... Pull #110 23 Apr 2026 05:02PM UTC shane-tw github
53.28
24847903587 fix/cross-package-enum Fix enum variations not resolved for cross-package enum types When a field annotated with {enum} has a type from another package (e.g. `pkg.SomeType`), getEnumVariations was never called with the correct type name. The SelectorExpr branch called ... Pull #110 23 Apr 2026 04:59PM UTC shane-tw github
52.29
24847670430 fix/cross-package-enum Fix enum variations not resolved for cross-package enum types When a field annotated with {enum} has a type from another package (e.g. `pkg.SomeType`), getEnumVariations was never called with the correct type name. The SelectorExpr branch called ... Pull #110 23 Apr 2026 04:53PM UTC shane-tw github
52.29
See All Builds (82)

Badge your Repo: kommentaar

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.

Could not find badge in README.

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

Refresh
  • Settings
  • Repo on GitHub
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