Changing all status codes from raw numbers to using fastapi.status #1319
Conversation
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
akanshadubey24
approved these changes
Aug 31, 2024
|
@alejsdev It seems that there is a problem with new pushes into the project! After I synched the new updates, it has a build problem on actions/checkout@v4. I wonder why this issue has happened? |
Hi @javadzarezadeh, I can confirm that this is an issue with the CI that is unrelated to your PRs. We're looking into it! 🙏 |
javadzarezadeh
force-pushed
the
refactor-status-code
branch
from
bfb3ad1 to
6c9b1fa
Compare
|
Moved to #1624 |
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.
I believe that using status codes via FastAPI (Starlette, actually!) instead of using raw numbers is more readable, consistent, and makes development easier.