Issue Summary:
You entered a large number in the “Spots in Your Car” field (probably beyond the valid range).
Then you entered a valid-looking smaller number (4).
It still shows the error “Not within valid range.” but also shows “Trip saved!” — which is contradictory.
Likely Problem:
The validation logic or UI state is not updating correctly after the invalid input is replaced with a valid one.
Possible Root Causes:
Stale validation state: The error message ("Not within valid range.") wasn't cleared after updating the input.
Frontend bug: The trip-saving logic is probably running even though there’s still a validation error visible.
Race condition or asynchronous validation where the component doesn’t re-check the field before submission.
"Trip saved!" is showing based on a previous valid state, even though the form now contains a validation error.
Suggestions for Fix:
Ensure that form validation is re-triggered on any change to the “Spots in Your Car” input.
Only allow "Trip saved!" to be displayed if all validations pass at the time of form submission.
Consider disabling the Save button until all inputs are valid.
Add console logs or debugging points to confirm when validation is triggered and what values are being checked.
It is provided in the User Manual and SRS document about interactive UI but not implementing.
Issue Summary:
You entered a large number in the “Spots in Your Car” field (probably beyond the valid range).
Then you entered a valid-looking smaller number (4).
It still shows the error “Not within valid range.” but also shows “Trip saved!” — which is contradictory.
Likely Problem:
The validation logic or UI state is not updating correctly after the invalid input is replaced with a valid one.
Possible Root Causes:
Stale validation state: The error message ("Not within valid range.") wasn't cleared after updating the input.
Frontend bug: The trip-saving logic is probably running even though there’s still a validation error visible.
Race condition or asynchronous validation where the component doesn’t re-check the field before submission.
"Trip saved!" is showing based on a previous valid state, even though the form now contains a validation error.
Suggestions for Fix:
Ensure that form validation is re-triggered on any change to the “Spots in Your Car” input.
Only allow "Trip saved!" to be displayed if all validations pass at the time of form submission.
Consider disabling the Save button until all inputs are valid.
Add console logs or debugging points to confirm when validation is triggered and what values are being checked.
It is provided in the User Manual and SRS document about interactive UI but not implementing.