MetagaussInc / Blazeforms-Revamped-Frontend

Contains all the latest revamped code for front-end of Blazeforms.
0 stars 0 forks source link

Validation Fixes #134

Closed charan-singh05 closed 3 years ago

charan-singh05 commented 3 years ago

Issue One

1- Select "Always" for "Require This Field", on Conditional Properties for any control. 2- Go to Submit, or launch the form after publishing or make "New Entry" through "Entries" page.

Problem: Submit button will not be enabled till required field is filled in. What should happen is that Submit button is enabled but clicking on it shouldnt submit the form and show error message next the fields that were marked as required. Right now, if there are too many fields on the form, and some of them are marked "Required", user has no way to know which ones are mandatory. So we should also display asterisk (*) next to the labels of the fields marked as required/always.

Issue Two

For all the controls on Form Builder that have Min to Max range, Max range should not be allowed to be less than Min value

Issue Three

Set default Max value to very high number. Refer to default Max values in following list.

_First Name, Last Name, Password: 499

Single Line Text, Multi Line Text, Payment: 9999

Currency, Number: 999999999_

If user clears this number by deleting it, but does not provide alternative value, or tries to set it to even much higher value than the default value we provided, then system should ignore it and revert back to default value. Anything lesser than max default value should be allowed and saved.

Issue Four

Min value for fields mentioned in First Name, Last Name, Password, Single Line Text, Multi Line Text, Payment, Currency above should be 0. For Number, min number should be -999999999. If user tries to delete it or enter a negative number, then it should be ignored, and system should revert it back to 0.

Issue Five HIGH SECURITY RISK If we try to write whole any malicious code in text boxes, such as SQL query injection, or the whole of code snippets, it should be normalized with escape characters and then saved. Otherwise this can be a huge sanitization issue attracting all sorts of hackers into our DB.

charan-singh05 commented 3 years ago

Issue fix verified.