Station End Points Return Codes

[joannekoch]

1. api/stations/create - returns 204 - HTTP 204 No Content - instead of a Successful Response. Throws an error in code when expecting a response with await response.json(); Please return a Successful Response.

2. api/stations/create - returns an error - SyntaxError: Unexpected token 'T', "Traceback "... is not valid JSON when try to create a station with the same name. Please return the correct error below:
   django.db.utils.IntegrityError: duplicate key value violates unique constraint "core_station_name_key"
   DETAIL: Key (name)=(test) already exists.
   Internal Server Error: /api/stations/create

3. api/stations/create and api/stations/set_location do not update the Station File.

4. api/stations/set_location throws either error: 204 error (no content) or SyntaxError: Unexpected token 'T', "Traceback "... is not valid JSON when try to set a station location with the same location & time. Please return Sucdcess or the correct error below:

   A location already exists at the given start_time

5. Add delete station ep in case admin creates a station by accident.

[joefutrelle]

Thanks @joannekoch -- these are older endpoints which is why they aren't working as expected and aren't handling errors properly.

Note that 204 is not an error code--all response code in the 200 block indicate success. "No content" means that the request succeeded and that nothing needed to be returned--which is generally how REST APIs respond to a successful "create" request.

Note that 500s are going to come back from the server currently with tracebacks in the response, but that's only because the service is currently configured with debugging on. The error that needs to be returned for these database constraint violations would be 409 ("Conflict").