208 - Added endpoints for getting, posting and deleting jobs.

[cowmanjoe]

🔨 Changes

• Added POST/job for posting a single ZipRecruiter job, and POST/jobs for posting an array of them
• Added DELETE/job for deleting a job by id
• Added GET/job for getting a job by id

  :squirrel: Testing instructions

  1. Run the job_server and make sure the database is running as well
  2. Go to the Swagger UI at http://localhost:5000/swagger
  3. Test the endpoints as documented there

EDIT: these were old instructions after 1 before Swagger support, leaving them here in case you want to use them for whatever reason.

2. Open Postman or whatever program for hitting API endpoints
3. POST an array of jobs by taking the entire jobs object from data_acquisition/sample_response.json and putting it in the request body as JSON
4. POST a job by taking a single job object from the jobs array in data_acquisition/sample_response.json and putting it in the request body as JSON
5. GET a job by taking the ID from the response to the POST in (4) and calling GET/job?id={ID}
6. DELETE a job by using the same ID and calling DELETE/job?id={ID}
7. Verify the job is deleted by calling GET/job?id={ID}
8. Try other edge cases like incorrect ID and anything else you can think to see if it breaks

:clipboard: Checklist

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes

[cowmanjoe]

One problem I see with this change is that there isn't a POST call for just a Job as we have defined it, only for ZipRecruiter job objects. Do you guys think we need to implement this now, or should it be a different ticket? Also, should the name of this endpoint be different since it is specific to ZipRecruiter? Maybe in the future I could implement it so that there is a field in the request that specifies what kind of schema (i.e. ZipRecruiter, our schema, Indeed).

[frostyshadows]

@cowmanjoe would it make more sense for postJob to take in a generic job and expect the conversion to be done by the data acquisition part instead instead?

[cowmanjoe]

@sherry I think I agree about posting jobs as our job schema rather than ZipRecruiter's