Resolve OpenAPI $ref response objects during DSL v4 import Problem DSL v4 OpenAPI import…
- User
Resolve OpenAPI $ref response objects during DSL v4 import
Problem
DSL v4 OpenAPI import currently misses valid response objects that are expressed as
$refs.import_responsecallsselect_json_response, andselect_json_responselooks forcontentdirectly on each response object without first resolving$ref.Code references:
crates/coral-spec/src/v4/mod.rs:972crates/coral-spec/src/v4/mod.rs:1290
A valid OpenAPI shape like this is treated as if the operation has no JSON response:
responses: '200': $ref: '#/components/responses/Foo' components: responses: Foo: content: application/json: schema: type: array items: type: objectImpact
The importer falls through to
OutputCardinality::None, which causes otherwise valid read operations to be hidden/dropped from the generated projection catalog. This can make major portions of a real OpenAPI descriptor disappear from DSL v4 sources.Acceptance criteria
- Response
$refs under operation responses are resolved before selecting JSON responses. - Missing or external response refs produce diagnostics consistent with existing schema/parameter ref diagnostics.
- A regression test covers a
200response that references#/components/responses/...and verifies the projection is published.
Interface
No new interfaces are introduced.
- Assistant
I'll inspect the OpenAPI import path and how other
$reftypes are resolved so we can apply the same pattern to response refs. - Assistant
Resolving response
$refs inselect_json_responseusing the sameresolve_refpath as parameters and request bodies. - Assistant
Fixing a bug:
candidateswas consumed twice in the selection logic. - Assistant
Adding the regression test:
- Assistant
Merging duplicate
implblocks for cleanliness. - Assistant
Response
$refs are now resolved before JSON response selection, matching how parameters and request bodies are handled.Change
select_json_responseis now a method onOpenApiImporterthat callsresolve_refon each response object before looking forcontent.application/json. That reuses the existing ref machinery:- Internal refs (
#/components/responses/...) are resolved viadocument.pointer() - External refs emit
OPENAPI_EXTERNAL_REF_UNSUPPORTED - Missing refs emit
OPENAPI_REF_NOT_FOUND
Regression test
importer_resolves_response_refs_before_selecting_json_contentcovers a200response with$ref: '#/components/responses/Foo', assertsOutputCardinality::List, and verifies theitemstable projection is published.All 9 OpenAPI tests pass.
- Internal refs (
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →
- fable-5Compare side by side →