fix(Annotations): add the Info Object's summary field - #2194
Merged
Conversation
The Info Object gained summary in 3.1; classic had no property for it, so it could not be written. The 3.0 document omits it silently in jsonSerialize(), matching both the License::$identifier precedent and the spec compiler's own handling - uniform drop diagnostics are a question for the wider Since mechanism, not this field. The new InfoObject fixture pins the full Info Object in all three modes.
DerManoMann
added a commit
to DerManoMann/swagger-php
that referenced
this pull request
Sep 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
The Info Object gained
summaryin OpenAPI 3.1; classic has no property for it, so it cannot be written — the spec pipeline has carried it all along. Fourth fix under the classic spec-compliance carve-out (#2190).The 3.0 document omits the field silently, matching both the
License::$identifierprecedent classic-side and the spec compiler's own handling ofsummary— whether such drops should warn uniformly is a question for a general mechanism, not one field.Changes
Annotations\Infogainssummary, omitted from 3.0 documents injsonSerialize()Attributes\Infotakessummaryas a constructor parameterHybridBridge::convertInfo()carries it into the spec pipelineScratch/InfoObject{,-spec}fixture pins the full Info Object in all three modes; the 3.0 expectation omitssummary