Skip to content

Fix PUT operations: fully replace the content of a record with a new one #146

New issue

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

Merged
merged 2 commits into from
Feb 10, 2021

Conversation

imcaizheng
Copy link
Contributor

Screenshots as Verification

  1. PUT /jobs/:jobId

    updateJob

  2. PUT /jobCandidates/:jobCandidateId

    updateJobCandidate

  3. PUT /resourceBookings/:resourceBookingId

    updateResourceBooking

@@ -2003,7 +2003,6 @@ components:
required:
- projectId
- userId
- status
Copy link
Contributor Author

@imcaizheng imcaizheng Feb 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believed that, in order to be consistent, in the PUT operation status should have a default value like in the POST operation. So status is no longer being a required field.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, agree 👍

@maxceem
Copy link
Contributor

maxceem commented Feb 10, 2021

@imcaizheng PR looks good to me. Could you please, resolve the merge conflict after merging the previous PR.

@imcaizheng
Copy link
Contributor Author

@maxceem PR updated.

Copy link
Contributor

@maxceem maxceem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for so quick update @imcaizheng.
Works good as per local testing.

@maxceem maxceem merged commit c887a76 into topcoder-platform:dev Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants