Describe the problem
The user can type an empty value into the usage
prompt and it will result in the server crashing due to poor error-handling.
Actual behavior
When a user is using the app, it is possible to crash the server resulting in more than one user not being able to use the service for a period of time. This is obviously a problem we should address.
There is not a design in place for the error on screen so it just renders simply the error message on screen, which is coming from the client not handling the error correctly either. The client is not parsing the JSON from the server because the server isn't responding with JSON right now. (Come to think of it maybe the server isn't crashed cause do not see error 500)
Expected behavior
The server should have proper error handling. The frontend should have proper error handling. It would be awesome to have a design for the front end error.
To Reproduce
Steps to reproduce the behavior:
- Go to Our Development Deployment
- Scroll down to the input with
Coordinate colors for my outfit
in the contents and replace it with nothing. It should show a placeholder of 'usage'.
- Click on the Get Recommendations button.
- See error
Screenshots
Your Environment:
- Chrome Version 125.0.6422.142 (Official Build) (64-bit)
Additional Information
There are also duplicate elements for inputting a usage prompt and submitting the form but only the ones on the left work, which is not intuitive. This bug fix could also address this issue as we are all potentially working on something within it.
And I apologize to anyone that may be upset for deciding to use this tool over Jira for such a thing; but we should utilize what is right for the job and this is the best tool for this job.