Environment
Development environment.
Steps to Reproduce
Sessions tab
Although the error is error message is correct it could be rephrased by doing the following:
The value of a/an feedback session name should be no longer than 38 characters. because the input validation anyway doesn't allow instructor to input more than 38 characters.~ Correct the grammar of The value of **a/an feedback** session name should be no longer than 38 characters.The field Session Name should not be empty@tshradheya Are you working on this or can I take it?
Can I take up this issue?
I am not working on this. ~Since @sukanta-27 asked first, I think he can take up this issue~
@tshradheya Thanks :smile:
@sukanta-27 I'd advise against taking new ones because you're already involved in few other things, particularly related to private sessions.
@junkiattan you can go ahead.
Okie! @wkurniawan07 @tshradheya
Actually for the student side, the input is validated client-side without making requests to the server to validate the message. Should we do the same for the instructor side?
Actually for the student side, the input is validated client-side without making requests to the server to validate the message. Should we do the same for the instructor side?
Our general policy is to favor server-side validation. Although it is slower, it avoid the duplication of validation, once in JS and once in Java.
Remove The value of a/an feedback session name should be no longer than 38 characters. because the input validation anyway doesn't allow instructor to input more than 38 characters.
The error still needs to be there in case the user bypasses the client-side validation.
"Slower" or "duplication" or "favor" is not the issue. Server-side validation is a must (especially in RESTful architecture, which we are not) because it is the only type that users cannot bypass.
I think that's what @damithc meant by duplication - whenever we implement client-side validation, it is a duplication of validation because we already have server-side validation (which is a given, like you said). We favour pure server-side validation, as opposed to client-and-server-side validation.
Most helpful comment
I think that's what @damithc meant by duplication - whenever we implement client-side validation, it is a duplication of validation because we already have server-side validation (which is a given, like you said). We favour pure server-side validation, as opposed to client-and-server-side validation.