Errors would not load into the Visit form, and the user who is reviewing an entered visit would have to dart back and forth between the VisitsListView template and the Visit itself.
After this PR
Errors now load into the form in the category where they are relevant. They do however still need formatting, as they are raw errors that are not incredibly user-friendly:
n.b. these are also the errors in the tooltips in the VisitsListView. Tidying them up (potentially in the template tag which finds and loads them into the template) would fix both the tooltips and form in this regard.
Before this PR
Errors would not load into the Visit form, and the user who is reviewing an entered visit would have to dart back and forth between the VisitsListView template and the Visit itself.
After this PR
Errors now load into the form in the category where they are relevant. They do however still need formatting, as they are raw errors that are not incredibly user-friendly:
n.b. these are also the errors in the tooltips in the VisitsListView. Tidying them up (potentially in the template tag which finds and loads them into the template) would fix both the tooltips and form in this regard.