Skip to content

Improve error message for required fields #1255

Closed

Description

@PVince81

Using the required-attribute to generate error messages means that they might at times be misleading. In the example below the user need to choose one of the four checkboxes, but the error message simply says that the user must check the first one to continue. Since only the first object with this attribute gets an error message this can be quite confusing.

image

Suggestion:

  • Design and implement custom error messages. They should tell what the issue is and how to resolve it where possible
  • They must be connected to their form objects in the code
  • Avoid using the required-attribute

Activity

  1. added
    bugSomething isn't working
    designRelated to the design
    on Jul 15, 2022
  2. added this to the 3.1 milestone on Aug 27, 2022
  3. modified the milestones: 3.1, 3.2 on Feb 20, 2023
  4. modified the milestones: 3.2, 3.3 on Mar 5, 2023
  5. modified the milestones: 3.3, 3.4 on May 22, 2023
  6. modified the milestones: 3.4, on Oct 13, 2023
  7. modified the milestones: , 4.0, 4.1 on Nov 27, 2023
  8. modified the milestones: 4.1, Maybe someday on Jan 18, 2024
  9. modified the milestones: Maybe someday, 5.3 on Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    1. to developAccepted and waiting to be taken care ofbugSomething isn't workingdesignRelated to the design

    Type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions