Document form error message pattern

Description

There is no pattern for adding error messages to forms in the OpenLMIS-UI. There needs to be a simple documented pattern that could be reused by other implementers, or have core behavior changed.

Acceptance Criteria

  • Styleguide page clearly explains how to add error messages to a form

  • Styleguide page that explains how to add an error message to a specific input

  • Tickets added for forms that don't align with specification - Created for the forms that don't match standards

Activity

Show:
Nick Reid
July 12, 2017, 9:51 PM
Edited
Sam Im
July 12, 2017, 11:25 PM

The validations when creating an R&R template work differently than this, should it be called out somewhere in the style guide to make sure that isn't changed?

Nick Reid
July 13, 2017, 2:37 AM

Good point — maybe we should make a ticket about moving the requisition-template error messages to look and work like other table-based items? Like the requisition-product-grid?

Sam Im
July 13, 2017, 4:33 AM

We'll need to have a separate discussion about the requisition template because each field that has an error and specific error message associated, which is required for the admin to know what they are doing wrong and how to correct it before saving the template. Aside from that, I can mark this done if you agree.

Nick Reid
July 13, 2017, 6:17 PM
Edited

Cool — I'm going to mark as done, and create an associated task to reformat Requisition Template error messages ()

Done

Assignee

Sam Im

Reporter

Nick Reid

Labels

Story Points

5

Time remaining

0m

Components

Sprint

None

Fix versions

Priority

Major