Scan API #67

Closed
opened 2020-12-31 16:41:17 +00:00 by niggl · 3 comments
Owner

We need api endpoints for scans (any type).

  • Get all scans
  • Get a single scan
  • Create a new scan (normal)
  • Update a scan's information
  • Delete a scan

And endpoints for the scan stations

  • Get all scan stations
  • Get a single scan station
  • Create a new scan station
  • Update a scan station's information
  • Delete a scan station

We also need test for all new endpoints:

  • scans get
  • scans add
  • scans update
  • scans delete
  • scanstations get
  • scanstations add
  • scanstations update
  • scanstations delete
We need api endpoints for scans (any type). * [x] Get all scans * [x] Get a single scan * [x] Create a new scan (normal) * [x] Update a scan's information * [x] Delete a scan And endpoints for the scan stations * [x] Get all scan stations * [x] Get a single scan station * [x] Create a new scan station * [x] Update a scan station's information * [x] Delete a scan station We also need test for all new endpoints: * [x] scans get * [x] scans add * [x] scans update * [x] scans delete * [x] scanstations get * [x] scanstations add * [x] scanstations update * [x] scanstations delete
niggl added this to the Donations&Scans milestone 2020-12-31 16:41:17 +00:00
niggl added the
priority:medium
enhancement
labels 2020-12-31 16:41:17 +00:00
niggl referenced this issue from a commit 2021-01-03 17:48:08 +00:00
niggl added the
status:doing
label 2021-01-03 18:37:39 +00:00
niggl referenced this issue from a commit 2021-01-07 15:38:44 +00:00
niggl referenced this issue from a commit 2021-01-07 16:03:41 +00:00
niggl added a new dependency 2021-01-07 17:59:36 +00:00
Author
Owner

I implemented most endpoints for the scanstations.

We have two options of "disableing" a scanstation:

  1. Just delete it -> This would mean that all scans created by this station would lose their scanstation association (which currently can't be null) aka they can't be traced back to that specific station any more
  2. Add a "enabled" flag -> This is the safe and easy route, but begs another question: Update this value via put (which shouldn't allow changeing anything but the enabled flag and description) or add a /disable route

Imo: We should go with 2. and a partial put.
@philipp What do you prefer?

I implemented most endpoints for the scanstations. We have two options of "disableing" a scanstation: 1. Just delete it -> This would mean that all scans created by this station would lose their scanstation association (which currently can't be null) aka they can't be traced back to that specific station any more 2. Add a "enabled" flag -> This is the safe and easy route, but begs another question: Update this value via put (which shouldn't allow changeing anything but the enabled flag and description) or add a /disable route Imo: We should go with 2. and a partial put. @philipp What do you prefer?
niggl referenced this issue from a commit 2021-01-07 18:18:28 +00:00
niggl referenced this issue from a commit 2021-01-07 18:19:22 +00:00
niggl referenced this issue from a commit 2021-01-07 18:36:59 +00:00
niggl referenced this issue from a commit 2021-01-07 19:04:16 +00:00
niggl referenced this issue from a commit 2021-01-07 19:16:17 +00:00
Author
Owner

Since the creation of runnercards is a prequesite for trackscans i'm going to move all trackscans related tests and debugging to a new issue.

Since the creation of runnercards is a prequesite for trackscans i'm going to move all trackscans related tests and debugging to a new issue.
niggl added a new dependency 2021-01-08 15:36:53 +00:00
Author
Owner

The new issues are: #77 and #78

The new issues are: #77 and #78
niggl referenced this issue from a commit 2021-01-08 15:47:54 +00:00
niggl referenced this issue from a commit 2021-01-08 16:27:57 +00:00
niggl referenced this issue from a commit 2021-01-08 16:42:07 +00:00
niggl referenced this issue from a commit 2021-01-08 17:37:34 +00:00
niggl referenced this issue from a commit 2021-01-08 18:34:40 +00:00
niggl referenced this issue from a commit 2021-01-08 18:37:28 +00:00
niggl closed this issue 2021-01-08 19:18:42 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: lfk/backend#67
No description provided.