[Peefy]

Fixes #181.

Since #180, a CRD with exactly one version gets a schema name after the bare Kind (e.g. Widget), dropping the version qualifier. Two defects, one root cause:

A. kcl import groups generated files into per-version directories by extracting the version from the file name (_v1, _v1alpha1, ...). A single-version CRD rendered as models/unknown/widget.k instead of models/v1/..., silently changing the import path of published modules (strimzi_kafka_operator.v1 -> ...unknown).

B. Two CRDs sharing a Kind across different API groups both rendered as models/widget.k: the CLI converts each YAML document of the input file into its own spec and generates each separately, so the second file silently overwrote the first (exit code 0).

Fix

• pkg/swagger/generator/names.go: append the version to the short root name unconditionally (Widget -> WidgetV1), so the file name always carries the version. When the same Kind+Version is declared by several API groups, every root of that class is additionally qualified with its group segments (example.com/other.com Widget -> ExampleComWidgetV1 / OtherComWidgetV1), keeping both definitions and preserving the group identity.
• pkg/kube_resource/generator/generator.go: GetSpecs/GetSpec now merge all YAML documents of one file into a single swagger spec, so every CRD of the file is generated in one run against a shared name registry, instead of one overwrite-prone generation per document. Side effect: the standalone binary now handles multi-document files instead of silently converting only the first document.
• pkg/swagger/generator/{model,language}.go: make rendered default/example values deterministic. RecoverMapValueOrder filled MapSlice slots from value.MapKeys() (random order) and toKclValue iterated maps via MapRange (random order), so the golden suite failed intermittently (~1 in 3 runs) on JSON key order.

Multi-version CRDs keep the names #180 introduced (WidgetV1 / WidgetV1alpha1); --long-names is unchanged. Golden fixtures regenerated: single-version model files now carry the _v<version> suffix.

Verification

The issue's reproducer now yields:

models/v1/example_com_widget_v1.k
models/v1/other_com_widget_v1.k
    replicas?: int        # no longer lost
    otherOnlyField?: int

and the generated package compiles and runs with kcl (schema instantiation, correct apiVersion defaults). go test ./... passes; the golden suite was run repeatedly to confirm the flake is gone.

Known limitation: the same Kind in different groups split across separate input files (kcl import -m crd a.yaml b.yaml) can still collide; 0.12.x avoided this via fully qualified names. The reported repro is a single multi-document file, which this fix covers.

[coveralls]

Coverage Report for CI Build 37960217708

Coverage increased (+2.0%) to 66.742%

Details

• Coverage increased (+2.0%) from the base build.
• Patch coverage: Could not be determined — this PR's diff is too large for GitHub to return (406 error at GitHub).
• 136 coverage regressions across 5 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

136 previously-covered lines in 5 files lost coverage.

File	Lines Losing Coverage	Coverage
pkg/swagger/generator/names.go	49	78.47%
pkg/kube_resource/generator/generator.go	41	72.91%
pkg/swagger/generator/spec.go	24	84.25%
pkg/swagger/generator/language.go	21	74.43%
pkg/swagger/generator/model.go	1	61.21%

---

Coverage Stats

Relevant Lines:	4895
Covered Lines:	3267
Line Coverage:	66.74%
Coverage Strength:	0.76 hits per line

---

💛 - Coveralls