If the user is creating a party and inputs an invalid input (anything that is not a valid wallet address or not a valid ENS), the user can still continue to create the party and the party would populate the invalid input as null.
To Reproduce
Steps to reproduce the behavior:
Begin the process of creating a pay party
Under either Voter or Candidate (or both), input an invalid wallet address or invalid ENS address (you can input any gibberish)
Although the tile turns red to symbolize an invalid input, the user can still continue the process and create a party all the way through.
Create the party and see blank, null tiles in the place where the invalid inputted wallet address will be.
Expected behavior
Begin the process of creating a pay party2.
Under either Voter or Candidate, if an invalid wallet address or invalid ENS address is inputted, the tile should continue to highlight it as red
however, the user should not be able to press Continue until all errors are resolved. The Continue Button should be grayed out until errors are resolved
Create the party and see only valid inputs in the final party voting screen
Screenshots:
Invalid input, but still able to press Continue button
Confirming a party with an invalid input. Notice how it populates as null in the signature request.
Final Vote Screen showing a null user to be voted on.
Describe the bug
If the user is creating a party and inputs an invalid input (anything that is not a valid wallet address or not a valid ENS), the user can still continue to create the party and the party would populate the invalid input as null.
To Reproduce Steps to reproduce the behavior:
Expected behavior
Screenshots: Invalid input, but still able to press Continue button
Confirming a party with an invalid input. Notice how it populates as null in the signature request.
Final Vote Screen showing a null user to be voted on.