Fix OpenAPI OperationId and add Summary/Description support#2445
Merged
jeremydmiller merged 1 commit intoJasperFx:mainfrom Apr 8, 2026
Merged
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
5 tasks
Member
|
Got it, but it took some follow up work., Thank you! |
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
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.
Problem
When setting
OperationIdon a Wolverine HTTP route attribute (e.g.[WolverineDelete("/{id}", OperationId = "DeleteStaffMember")]), the value is ignored in the generated OpenAPI document. Instead, theoperationId,summary, anddescriptionfields all default to a generated filename likeDELETE_id.This happens because
HttpChainimplementsIEndpointNameMetadata,IEndpointSummaryMetadata, andIEndpointDescriptionMetadata, but is never added to the endpoint's metadata collection — so the .NET OpenAPI document generator never sees these values.Changes
EndpointNameMetadata(OperationId)to endpoint metadata inBuildEndpoint()so the OpenAPI generator picks up the user-providedOperationIdSummaryandDescriptionproperties toWolverineHttpMethodAttributeto allow setting these in OpenAPI documentationIEndpointNameMetadata.EndpointNameandIEndpointSummaryMetadata.Summaryimplementations onHttpChainto use user-provided values instead ofToString()