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.
Add fixed-route single instance response shaping #163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Add fixed-route single instance response shaping #163
Changes from all commits
c922764File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a fixed route uses
ResponseShape.COLLECTION, this branch makes the runtime response a collection, but OpenAPI generation never consumesRoutingDefinition.responseShape():ThingifierApiSpec.applyFixedRoutePayloads()still registers the singular entity payload for successful fixed routes, andSwaggerizerderives its schema from that payload name. Generated clients therefore expect an object while the server returns the collection wrapper, so the documented payload/schema also needs to honor this shape.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When
respondWithSingleInstance()is placed on a normal generated instance rule—the addedThingifierApiSpecTestdoes this for/api/todos/{id}—a successful request returns 500 solely because the rule has no fixed mapping, even whenresponse.hasReturnedInstance()is already true. This turns an otherwise valid generated GET into a server error; accept an already-satisfied singleton response before enforcing fixed-route conversion, or reject this configuration during specification setup.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.