docs: Fix incorrect argument name in OpenApi ResponseSpec example #3017
Conversation
This file contains 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
provinzkraut
force-pushed
the
fix-openapi-example
branch
from
7e04010
to
9ba5345
Compare
|
Thanks @korneevm! |
|
@all-contributors add @korneevm for docs |
|
I've put up a pull request to add @korneevm! 🎉 |
|
Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/3017 |
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.
There is an incorrect argument name in the ResponseSpec example in the docs. ResponseSpec has no
modelarg, so when I tried to use this example I gotTypeError: ResponseSpec.__init__() got an unexpected keyword argument 'model'exception.The correct arg name seems to be
data_container, so I've updated the docs accordingly.