lfk/backend
2
0
Fork 0
Code Issues 1 Pull Requests Actions Projects Releases 40 Activity

Trackscan updateing is currently broken AF #163

New Issue
Closed
opened 2021-03-18 12:57:46 +00:00 by niggl · 0 comments
niggl commented 2021-03-18 12:57:46 +00:00
Owner
Copy Link

When you get a trackscan you just receive the id, runner, track, distance, laptime, timestamp and validity.

But to update such a trackscan you have to provide the scan's station -> Obvious problem....

In order to mitigate this i'm going to treat the station the same way we treat the cards: Purely documentational in the backend.

When you get a trackscan you just receive the id, runner, track, distance, laptime, timestamp and validity. But to update such a trackscan you have to provide the scan's station -> Obvious problem.... In order to mitigate this i'm going to treat the station the same way we treat the cards: Purely documentational in the backend.
niggl added this to the Project Quality of Life/Dev milestone 2021-03-18 12:57:46 +00:00
niggl added the
bug
priority:high
status:doing
 labels 2021-03-18 12:58:17 +00:00
niggl referenced this issue from a commit 2021-03-18 13:00:20 +00:00
The basic bugfix 🐞
niggl referenced this issue from a commit 2021-03-18 13:05:15 +00:00
Updated tests 🧪
niggl added
status:review_needed
 and removed
status:doing
 labels 2021-03-18 13:05:28 +00:00
niggl closed this issue 2021-03-18 15:09:10 +00:00
Sign in to join this conversation.
bugfix/163-trackscan_updates
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
priority:high
priority:low
priority:medium
question
More information is needed
status:blocked
status:doing
status:review_needed
wontfix
This won't be fixed
Complexity
Easy
The complexity is low
Complexity
Hard
The complexity is high
Complexity
Medium
The complexity is medium
Kind/Bug
Something is not working
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Question
A question
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status/Confirmed
This is indeed a bug/issue
Status
Doing
Somebody is working on this
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Status
Review needed
Needs a reveiw
No Label
bug
priority:high
status:review_needed
Milestone
No items
No Milestone Project Quality of Life/Dev
Projects
Clear projects
No project
Assignees
Clear assignees
niggl odit_bot philipp
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lfk/backend#163
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?