You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User model/repository is directly called and returned on entrypoints. If user is not found or there is some other kind of error (e.g. user_id doesn't exist when getting/updating/deleting) we get a 500 status code.
Suggested solution
Implement a UserService and also add pydantic fields, in which it will correctly run validations on entrypoint requests before returning and raise meaning HTTPError responses in case of not found IDs, etc.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
The text was updated successfully, but these errors were encountered:
Type of feature
🍕 Feature
Current behavior
User model/repository is directly called and returned on entrypoints. If user is not found or there is some other kind of error (e.g. user_id doesn't exist when getting/updating/deleting) we get a 500 status code.
Suggested solution
Implement a UserService and also add pydantic fields, in which it will correctly run validations on entrypoint requests before returning and raise meaning HTTPError responses in case of not found IDs, etc.
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: