Change how form fields are done

[rishabhpoddar]

• Make optional fields truly optional: Make optional form fields by default into empty string, improve error message for missing form fields and return a 400 in case of mismatch of form fields supertokens-node#300
• Improve error messages in case of fields missing: Make optional form fields by default into empty string, improve error message for missing form fields and return a 400 in case of mismatch of form fields supertokens-node#300
• Do not call form field validator for sign in and reset password code POST API supertokens-node#447
• Allow users to normalise form field inputs #589
• reorder form fields: Make it easier to reorder fields in the sign up form #296
• Disable default form fields (email and password) as well
• Allow any type of react component to be added as a form field.
  • Allow field decorators? Field decorators #36
• Allow flexible sign in form fields as well, and not just email and password.
• Pass forfields directly into signIn and signUp recipe functions so that overriding those for post sign up is easier (otherwise right now you have to override the api to pass form field as user context).
• Allow users to handle empty strings in form fields with a custom error message, even if they are marked as optional. For example, if password is marked as required, and if the user gives an empty string for it, then we will send a field required message - but that should be changeable by the dev.
• Fix this: Change how form fields are done #638 (comment)

[rishabhpoddar]

We have this old issue (in my sprint sheet) with the login forms in auth react where if you use CSS to change the order in which input fields are rendered in the login form, pressing TAB to go to the next form field would not always work correctly. This is because using CSS to change the order of the fields only affects the final render and not the element tree itself, and the browser uses the element tree when navigating between items with TAB.
For example if the element tree looks like this:

• Element 1 (CSS order 1)
• Element 2 (CSS order 3)
• Element 3 (CSS order 2)
  When tabbing from element 1, the browser will highlight element 2 even though on the UI the user would expect it to go to element 3.
  Since we are refactoring things in the form fields we may also want to look into this and see if we can make it easier for users to order the form elements.

15:39
This might have already been fixed, but just putting it out there

[ptdatta]

Hey @rishabhpoddar are all of them fixed?

[rishabhpoddar]

I dont think so @ptdatta