chore: Added operationId for operationObjects in OpenAPI specs #323
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.
Description
api/openapi.yaml
was missingoperationId
attributes for operationsObjects (documentation here).oapi-codegen seems to ignore this and generates the operationId's if they are absent. I added the identifiers to match the ones generated by oapi-codegen, so there are no changes in the generated
client/model/server.gen.go
. I confirmed this by runningmake api
and diffing the files.Code generation tested with openapi-python-generator.
Also ran the
make build
andmake test
to check for any failures, but no functionality has been changed.Type of Change
[x] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[ ] Documentation
[ ] Other (please describe)
Checklist