Skip to content

Nested Compositions - #74

Closed
wol-soft wants to merge 1 commit into
masterfrom
issue72_nestedComposition
Closed

Nested Compositions#74
wol-soft wants to merge 1 commit into
masterfrom
issue72_nestedComposition

Conversation

@wol-soft

Copy link
Copy Markdown
Owner

No description provided.

@wol-soft wol-soft added the bug Something isn't working label May 30, 2023
@wol-soft wol-soft self-assigned this May 30, 2023
@wol-soft wol-soft linked an issue May 30, 2023 that may be closed by this pull request
@coveralls

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 5119595183

  • 15 of 15 (100.0%) changed or added relevant lines in 3 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.04%) to 98.814%

Totals Coverage Status
Change from base Build 4893336589: 0.04%
Covered Lines: 2833
Relevant Lines: 2867

💛 - Coveralls

@wol-soft

Copy link
Copy Markdown
Owner Author

Superseeded by #166

@wol-soft wol-soft closed this Jul 16, 2026
@wol-soft
wol-soft deleted the issue72_nestedComposition branch July 16, 2026 20:12
wol-soft pushed a commit that referenced this pull request Jul 27, 2026
PR #74 targeted two composition bugs reported against a FedEx OpenAPI schema:
a crash on deeply nested allOf $ref chains, and oneOf branches containing only
an "example" keyword matching every input. The PR's own code no longer applies
(the composition architecture it patched was fully rewritten since), so only
its test schemas are reconstructed here against current master, pinning the
verified current behavior:

- Deeply nested allOf no longer crashes, but the composed property is never
  instantiated as an object (getCEO() returns a raw array despite a nested
  @return annotation).
- A root-level oneOf with an example-only branch still fails generation with
  "No nested schema for composed property" - a stricter form of the original
  crash.
- The same branch nested inside a property lets generation succeed, but the
  example-only branch is never skipped during validation, so valid input is
  rejected for matching two branches instead of one.

See .claude/issues/72/analysis.md and implementation-plan.md for the full
investigation and the patches still needed; no fix is applied in this commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error when generating classes with FedEx OpenAPI schema

2 participants