Required validations for check-boxes and drop-downs not honored in GitHub issue templates

[Elliria]

Select Topic Area

Bug

Body

I admit that it's possible that my syntax isn't correct, but I believe I've come across a validations bug in GitHub's YAML issue templates.

These two example questions specify the true attribute for the required option in the validations field, yet neither question is actually required for completing the issue report:

  # TEST OF REQUIRED QUESTION WITH CHECK-BOXES
  - type: checkboxes
    id: test_of_required_question_with_check_boxes
    attributes:
      label: Test - Is this question with check-boxes required?
      description: >
        It should be, but isn't.
      options:
        - label: One
        - label: Two
        - label: Three
    validations:
      required: true

  # TEST OF REQUIRED QUESTION WITH A DROP-DOWN MENU
  - type: dropdown
    id: test_of_required_question_with_a_drop_down_menu
    attributes:
      label: Test - Is this question with a drop-down menu required?
      description: >
        It should be, but isn't, and GitHub gives it a red asterisk as though it is.
      options:
        - One
        - Two
        - Three
    validations:
      required: true

Also, GitHub doesn't automatically put a red asterisk next to the question with the check-boxes at all, which indicates to the user that the question is optional. The issue report can be submitted without the user interacting with the check-boxes.

Also, GitHub automatically puts a red asterisk next to the question with a drop-down menu, which indicates to the user that the question is required, but the issue report can be submitted without the user interacting with the drop-down menu.

[codebydant]

This is related to #43859

[Elliria]

Thank you, but that's in reference to private and internal repositories, whereas mine is in reference to public repositories. Hopefully someone will fix it.

[Apaczer]

Still an issue in 2024? You can't enforce an user to pick a proper value from dropdown menu because form schema is always setting default: 0 which omits validations key. What's more the templates-docs suggest there isn't Default value for default attribute.

[Jonathan523]

I think for dropdown menu it is not applicable, but for checkboxes it becomes very useful and we need this validation.

[Elliria]

Since this is about not being able to do a test to determine if a user interacted with a required checkbox or required drop-down element, I think the drop-down menu also applies in this case. As you pointed out, it defaults to zero, so there's never a time where some sort of value isn't given to the drop-down element. That currently makes validation impossible for determining whether a user has interacted with a required drop-down or not, so I'd suggest that some sort of test should be made available to see if the value is non-zero, indicating that the user has made a choice.

[Elliria]

Related issues: #1693 and #9706.

[therealgladius]

I made a plugin for that: https://github.com/therealgladius/required-checkboxes-for-elementor-forms

[Elliria]

No idea what the actual cause is other than it's either not spitting out what it's supposed to or it is and something isn't receiving it. Why is the question and hopefully some kindly dev will take a look at it and fix it.