You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a 100 character length maximum on the search term enforced on the API. Currently if a user enters a term longer than 100 characters the UI shows them a generic error. For better UX we should:
respond to the API error with a more specific error based on the error returned from the API
validate search term length with a max of 100 characters on the frontend and disallow search for terms that are too long
The error from the API response looks like this
Acceptance criteria
respond to the API error with a more specific error based on the error returned from the API
validate search term length with a max of 100 characters on the frontend and disallow search for terms that are too long
More specific requirements around verbiage TBD
The text was updated successfully, but these errors were encountered:
)
* introduces client side validation of the query string size, and displays an error on submit click without submitting
* to handle a case where a request does go out from the client but returns with a validation error, error handling
system has been updated to pass relevant information to the client so that it can be handled
* fixes a bug that was preventing the search form state to be maintained in the case of an error.
Summary
There is a 100 character length maximum on the search term enforced on the API. Currently if a user enters a term longer than 100 characters the UI shows them a generic error. For better UX we should:
The error from the API response looks like this
Acceptance criteria
More specific requirements around verbiage TBD
The text was updated successfully, but these errors were encountered: