Required validations for check-boxes and drop-downs not honored in GitHub issue templates #45084
Replies: 3 comments 2 replies
-
This is related to #43859 |
Beta Was this translation helpful? Give feedback.
-
Still an issue in 2024? You can't enforce an user to pick a proper value from |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
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.
Beta Was this translation helpful? Give feedback.
All reactions