We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Both methods shown in the first part of the course are verbose and consist of the unnecessary logic.
Whenever we work with an API, we have a documentation in which one can find endpoints and how payload should look like
In case of a PUT request there is no need in updating one of the fields since PUT would modifies the whole resource anyway.
What you do relates more to PATCH request. Whenever you just want to modify a part of the resource. Let's say, the name { "name": "john doe" }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Both methods shown in the first part of the course are verbose and consist of the unnecessary logic.
Whenever we work with an API, we have a documentation in which one can find endpoints and how payload should look like
In case of a PUT request there is no need in updating one of the fields since PUT would modifies the whole resource anyway.
What you do relates more to PATCH request. Whenever you just want to modify a part of the resource. Let's say, the name
{
"name": "john doe"
}
The text was updated successfully, but these errors were encountered: