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
Describe the Bug
The search fields ("FOM Number" and "FSP ID") for the admin search are digits only, and should be restricted to 9 digits. But currently, user can input more than 9 digits and will encounter internal server error.
Expected Behaviour
Frontend admin UI search page:
Digits only fields.
Restrict to only 9 digits max.
If possible, remove leading '0' from user input.
Actual Behaviour
When more than 10 digits will have internal server error.
Screenshots
FSP ID:
FOM Number:
Desktop (please complete the following information):
On TEST environment.
This bug does not appear on local (it might be due to the fields uses some inline javascript and conflict to the content security policy that is applied on higher environment but not locally).
Additional context
The FOM Number and FSP ID field in database is Integer type, so no leading '0', meaning if user enters leading '0', it will be ignored and removed when saving into database.
Currently the implementation is using <input type="number>, may need to switch by using type="text". Public side has this case.
It might possibly be (just a thought) better to use custom (need to self build) Angular directive to restrict input to digit and max length 9). It might lead to better user input experience than just using <input type="text"> with event-listener to modify the input (like what public side does now).
The text was updated successfully, but these errors were encountered:
Describe the Bug
The search fields ("FOM Number" and "FSP ID") for the admin search are digits only, and should be restricted to 9 digits. But currently, user can input more than 9 digits and will encounter internal server error.
Expected Behaviour
Frontend admin UI search page:
Actual Behaviour
When more than 10 digits will have internal server error.
Screenshots
FSP ID:
FOM Number:
Desktop (please complete the following information):
Additional context
<input type="number>
, may need to switch by using type="text". Public side has this case.<input type="text">
with event-listener to modify the input (like what public side does now).The text was updated successfully, but these errors were encountered: