You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The field level error messages are not working when the "validation checks" span multiple lines in the validate code.
This is because the run.go (which holds the revel.DefaultValidationKeys) is generated using the "end" line number of the Check function but the validation.go revel file is expecting it to be keyed on the first/starting line number. It suspect it affects the booking example too.
The template extract that does not work
The user model validation for Name, starts on 40 and ends on 43
The generated run.go file has a map that keys the field on 43
The revel validate.go file extract that expects the key to be on the start line.
If I move the validation to be on 1 line, it works lol. This is expected because the first and last lines are the same number.
The text was updated successfully, but these errors were encountered:
Hello
The field level error messages are not working when the "validation checks" span multiple lines in the validate code.
This is because the run.go (which holds the revel.DefaultValidationKeys) is generated using the "end" line number of the Check function but the validation.go revel file is expecting it to be keyed on the first/starting line number. It suspect it affects the booking example too.
The template extract that does not work
The user model validation for Name, starts on 40 and ends on 43
The generated run.go file has a map that keys the field on 43
The revel validate.go file extract that expects the key to be on the start line.
If I move the validation to be on 1 line, it works lol. This is expected because the first and last lines are the same number.
The text was updated successfully, but these errors were encountered: