cbleek / jobarchive Goto Github PK

Let's start with an API. Swagger seems useful to me.

The API should be able to do the following:

register

A user should be able to register. A validated email is sufficient to send jobs.

delete

A user should be able to delete his data

edit

A user should be able to change his or her data

We should take Google as a model for the design of the API.

In the first step it should be possible to create a feed with many jobs or post a single job. Also it should be possible to get current jobs via API

OK. A question comes up.

What can use can do with RSS XML?
Submit or Retrieve. Can you explain more about this part?

@SJhumili

I'm thinking about the best way to collaborate. Swagger has nice team features, but they cost money and make the project dependent on swagger.io.

I wonder how I'm going to make a change to the API.

Your last commit changed 2 files. How did you do that?

So far I thought you only had to change one file in the Github repo. I had imagined that I would cut&paste the last version of the API into my sagger editor, make changes, and then cut&paste the new version into my checked out GIT Repo to push the change.

Can you please describe how we should make changes to the API?