JackPrince/GoBDLogBook
JackPrince/GoBDLogBook
Watch
1
1
Fork
You've already forked GoBDLogBook
 0
Code Issues 3 Pull requests Projects Releases Wiki Activity Actions

[M3] Inline Field Errors & Pre-Flight Validation Checks #5

New issue
Closed
opened 2026-09-04 15:00:19 +02:00 by JackPrince · 0 comments
JackPrince commented 2026-09-04 15:00:19 +02:00
Owner
Copy link

Part of Epic #2

Description

Improve error transparency so drivers understand why a trip cannot be saved, replacing generic toasts with inline field errors and pre-flight checklist validation.

Tasks

  • Propagate backend HTTP 422 payload.errors through ApiClient (api.ts) down to the form.
  • Render field-specific error messages beneath offending input fields in TripFormCard.tsx.
  • Implement a pre-flight checklist above the submit buttons:
    • Start odometer matches previous trip's end odometer
    • End time is strictly after start time
    • End odometer is greater than start odometer
    • No temporal overlap with existing trips
    • Mandatory confirmation fields completed (for final submit)
  • Add positive visual cues (green checkmarks, trip distance badge).

Acceptance Criteria

  • Drivers receive instant, localized error indicators on exact fields instead of a generic "The given data was invalid" toast.
Part of Epic #2 ## Description Improve error transparency so drivers understand why a trip cannot be saved, replacing generic toasts with inline field errors and pre-flight checklist validation. ## Tasks - [ ] Propagate backend HTTP 422 `payload.errors` through `ApiClient` (`api.ts`) down to the form. - [ ] Render field-specific error messages beneath offending input fields in `TripFormCard.tsx`. - [ ] Implement a pre-flight checklist above the submit buttons: - [x] Start odometer matches previous trip's end odometer - [x] End time is strictly after start time - [x] End odometer is greater than start odometer - [x] No temporal overlap with existing trips - [x] Mandatory confirmation fields completed (for final submit) - [ ] Add positive visual cues (green checkmarks, trip distance badge). ## Acceptance Criteria - Drivers receive instant, localized error indicators on exact fields instead of a generic *"The given data was invalid"* toast.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
No results found.
Labels
Clear labels   
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
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
Need More Info
 Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
JackPrince/GoBDLogBook#5
No description provided.