Added FastAPI Body to handle request body, causing an error. #127
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
Signed-off-by: Youngjin Jo <youngjinjo@megazone.com>
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.
Category
Description
Added
data: dict = Body()to thecreate_eventmethod to explicitly handle the request body as a dictionary. This change was intended to ensure that the incoming JSON payload is correctly parsed and accessible within the method. However, this modification caused an error, likely due to a conflict with the existing request parsing logic or parameter handling within the method.To avoid this issue, use
Body(default={})without therequestparameter. If you want to userequest, removeBody(default={}).Known issue
Using
requestand FastAPI'sBody()together in thecreate_eventmethod causes an error when the POST request has no body.