-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#7285] Live Server: disallow team name to be valid email #9471
Conversation
Closing and re-opening since PR was targeted at wrong branch previously. |
Ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -144,6 +144,8 @@ | |||
+ "The value of '${fieldName}' field should be no longer than ${maxLength} characters."; | |||
public static final String INVALID_NAME_ERROR_MESSAGE = | |||
ERROR_INFO + " " + HINT_FOR_CORRECT_FORMAT_FOR_INVALID_NAME; | |||
public static final String TEAM_NAME_IS_VALID_EMAIL_ERROR_MESSAGE = | |||
"The field " + TEAM_NAME_FIELD_NAME + " is not acceptable to TEAMMATES as team name can't be a valid email"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"As team name can't be a valid email" sounds quite weird. Suggest the following rephrase:
... is not acceptable to TEAMMATES as the suggested value for team name can be mis-interpreted as an email.
Also, team name
is the value for the constant TEAM_NAME_FIELD_NAME
so let's reuse it.
Updated, ready for review! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Received this new error from the live server today. Could it be related to this PR?
|
Hi prof, I think it's not relevant. |
Part of #7285
Disallow team name to be valid emails.