Chi: generate Unimplemented implementation#1090
Merged
1 commit merged intooapi-codegen:masterfrom Jul 28, 2023
Merged
Conversation
similar as a grpc-go uses
Contributor
Author
|
@deepmap-marcinr please look at this pr =) |
ghost
merged commit 
debuggerpk
pushed a commit
to breuHQ/oapi-codegen
that referenced
this pull request
Sep 18, 2023
similar as a grpc-go uses
danicc097
pushed a commit
to danicc097/oapi-codegen
that referenced
this pull request
Aug 31, 2024
similar as a grpc-go uses
This pull request was closed.
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.
Update chi-interface.tmpl to generate an implementation for ServerInterface that always returns a
http.StatusNotImplemented.The Unimplemented server can be used like this (assuming the code is generated in package spec):
Using Unimplemented is optional, but might help when prototyping APIs or in case the OpenAPI spec is managed in a separate repo and mutliple developers.
grpc-go uses a similar strategy. For example see the examples/route_guide/server/server.go file.
ref: #631