@@ -6,15 +6,15 @@ Group members: Job Nestor, Johannes Borgen, Bjørnar Larsen
## Status
This endpoint returns the http status of the the 2 API's we use as well as checking connectivity with the database.
You can view this endpoint by sending a GET request to: .../altocumulus/v1/status/
You can view this endpoint by sending a GET request to: <code>/altocumulus/v1/status/</code>
## Turer
This endpoint returns a list of different routes it takes can take 2 parameters ?limit="int" and &skip="int".
If they are not specified it wil set limit to 20 and it wont skip (start at 0)
The endpoint can be reached by a get request to /altocumulus/v1/turer
The endpoint can be reached by a get request to <code>/altocumulus/v1/turer</code>
## Tur
This endpoint can be reached at /altocumulus/v1/tur/524081f9b8cb77df150007fa.
This endpoint can be reached at <code>/altocumulus/v1/tur/524081f9b8cb77df150007fa</code>.
The string at the end is the id of the trip and can be replaced with any other valid id gotten from for example the turer endpoint
The endpoint provides more information about the route as well as weatherforecast and reviews stored in the database.
...
...
@@ -29,7 +29,7 @@ By sending a Post request with a payload you can add a review to the database. E
Navn, turid and beskrivelse has to be a string and terningkast has to be a number between 1 and 6. If you add a review
to the database it wil respond with the reviewID, this can be used to delete
#### Delete
By sending a Delete request to /tur/"ID", Where id is the string returned in the post endpoint wil delete the review from the Database
By sending a Delete request to <code>/altocumulus/v1/tur/"ID"</code>, Where id is the string returned in the post endpoint wil delete the review from the Database
## Report
...
...
@@ -54,13 +54,13 @@ brief description of the original project plan, and what has and has not been ac
on a given day.
What made this difficult was firstly, that we had very few API calls. This, however
was mitigated by one of our group members gaining developer access.
was mitigated by one of our group members gaining a developer token.
The second thing We also struggled with, was converting XML to JSON. This worked out in the end,
as we started to develop procedures to ectract the data and fields that we needed
from the XML file.
Lastly we struggled with getting a good test coverage, as we worte most of the code
Lastly we struggled with getting a good test coverage, as we wrote most of the code
before we wrote the tests.
###### What new has the group learned
...
...
@@ -68,7 +68,7 @@ brief description of the original project plan, and what has and has not been ac
about the challenges faced by developers in their adily lives, and have therefore
understood why we do things a certain way. As well as why we use ceratin workflows.
An couple of exaples on this would be:
An couple of examples on this would be:
* Using branches correctly to be able to develop without destroying someone
elses or your own work.
* Using good ommenting to understand what other team members have done, and also allow
