omnidoc/generateApiDoc.ts (1)

99-106: Cover the new 6-variant cutoff with boundary tests.

Line 100 changes a behavior boundary, but there’s no explicit spec for unions of exactly 5 and 6 variants. Please add boundary tests so this cutoff is locked and future refactors don’t silently revert it.

Proposed test additions

diff --git a/omnidoc/processType.spec.ts b/omnidoc/processType.spec.ts
@@
 describe('processType', () => {
+  it('should inline unions with 5 variants', () => {
+    const input = ['"a"', '"b"', '"c"', '"d"', '"e"'];
+    expect(processType(input, false)).toBe('"a" | "b" | "c" | "d" | "e"');
+  });
+
+  it('should inline unions with 6 variants', () => {
+    const input = ['"a"', '"b"', '"c"', '"d"', '"e"', '"f"'];
+    expect(processType(input, false)).toBe('"a" | "b" | "c" | "d" | "e" | "f"');
+  });
+
+  it('should collapse unions with 7 variants', () => {
+    const input = ['"a"', '"b"', '"c"', '"d"', '"e"', '"f"', '"g"'];
+    expect(processType(input, false)).toBe('(union of 7 variants)');
+  });
+
   it('should handle simple unions', () => {
     expect(processType(['string', 'number'], false)).toBe('number | string');
   });

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@omnidoc/generateApiDoc.ts` around lines 99 - 106, Add unit tests that assert
the union-formatting behavior at the new 6-variant boundary: create tests that
feed the logic (the code using isInline and uniqueParts in generateApiDoc.ts)
with exactly 5 and exactly 6 distinct union variants and verify the output is
the alphabetically sorted "A | B | C ..." string (i.e., joined with ' | '), and
also include a test with 7 variants to assert the alternative path (not joined)
still applies; locate the union formatting logic by the symbols isInline and
uniqueParts in generateApiDoc.ts and add these cases to the existing test suite
so the 5/6/7 variant behavior is locked.