allow normal topcoder members to create jobs and update/delete the jobs #21
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.
Test updated access rule for jobs
Postman collection is updated. Please run the following requests in Postman from top to bottom for verification.
jobs > create job with booking manager
jobs > create job with member success
jobs > put job with member 403
jobs > put job with member success
jobs > patch job with member 403
jobs > patch job with member success
jobs > delete job with member 403
jobs > delete job with member success
Test if user not found issue got fixed in JobService
You should first create a member token with userId that can be found in v3/users while missing in v5/users.
Then update the member token in Postman environment and run request
jobs > create job with member success
for verification.For example, I was using this token for test:
The token is for userId
106620
.The
jobs > create job with member success
request ran successfully with the token and here is example console logs:Notice the createUbhanUser function was called since the userId
106620
initially was not in v5/users.