You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(validator): accept response Content-Type for content negotiation
Add optional $responseContentType parameter to OpenApiResponseValidator::validate().
When provided, non-JSON content types defined in the spec are skipped (success),
undefined types produce a failure, and JSON-compatible types proceed to schema validation.
Move the Content-Type mismatch logic from ValidatesOpenApiSchema trait into the
validator itself for a single source of truth.
Closes#22
"Response Content-Type '{$normalizedType}' is not defined for {$method}{$matchedPath} (status {$statusCode}) in '{$specName}' spec. Defined content types: {$defined}",
89
+
]);
90
+
}
91
+
92
+
// JSON-compatible response: fall through to existing JSON schema validation.
0 commit comments