The discussion revolves around improving the UX on signup when a user has not completed all required fields. sam points out that the current error message is not helpful and suggests two improvements: scrolling to the unfilled field and making the error message more specific. They also suggest removing the disabled button and instead popping an error that teaches users why they cannot create an account.
codinghorror notes that having many required fields can be a problem, but agrees that making the error message more literal can be a good fix. sam responds that four required fields is not excessive.
sam requests that the error message be updated to specify the exact field that is missing, and nathank agrees that this would have helped in their previous experience with signing up multiple users. vinothkannans confirms that the correct error message has been added and merged in PR #9643.
Guess what I did not fill?
That’s right … good guess:
Instead:
We should at least scroll it so the field that is not filled in is on the screen
We should possibly make error message more specific: "You have not completed the Sector field".
Also:
We should stop doing this:
Button should not be disabled ever, just pop an error that teaches users why they can not create an account.
I mean, maybe – but if you have that many required fields you are shooting yourself in the foot so hard that the floor underneath you may collapse at any time.
Easiest fix for the moment is to be literal in the error about which field of the 62 required was not filled out.
4 required fields is A LOT, but not a super catastrophe imo, the fold when signing in via GitHub is just in a super unfortunate spot.
@vinothkannans 여기서 오류 메시지를 수정해 주실 수 있나요?
“XYZ” 값은 필수입니다.
즉, 다음과 같은 형태로요.
“Sector” 값은 필수입니다.
첫 번째 누락된 필수 필드를 선택해서 표시하면 됩니다.
짧은 시간 안에 많은 사용자를 등록해야 하는데 사용자 필드가 너무 많았던 문제 해결에 분명 도움이 되었을 것입니다. 이 문제를 해결해 주셔서 감사합니다.
올바른 오류 메시지가 이제 아래 열린 PR에 추가되었습니다
P.S. 병합되었습니다
