Boolean field does not handle requiredness correctly #1483

Closed
opened 2026-01-09 21:35:07 +01:00 by magicfelix · 5 comments
Member

Due to boolean fields mostly being non-null, the frontend marks those as required, resulting in the following behaviour.

While creating a new object, that has a boolean field, the save button remains disabled until the boolean field is set to true. One can set it to false afterwards and save the object.

Due to boolean fields mostly being non-null, the frontend marks those as required, resulting in the following behaviour. While creating a new object, that has a boolean field, the save button remains disabled until the boolean field is set to true. One can set it to false afterwards and save the object.
Owner

assigned to @hansegucker

assigned to @hansegucker
Owner

created branch 1483-boolean-field-does-not-handle-requiredness-correctly to address this issue

created branch [`1483-boolean-field-does-not-handle-requiredness-correctly`](/AlekSIS/official/AlekSIS-Core/-/compare/master...1483-boolean-field-does-not-handle-requiredness-correctly) to address this issue
Owner

mentioned in merge request !3751

mentioned in merge request !3751
Owner

Can you please provide a concrete example? Can't reproduce this right now.

Can you please provide a concrete example? Can't reproduce this right now.
Owner

mentioned in commit 222438560a

mentioned in commit 222438560a97e0854bbd82606de305ef25b6f3f8
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aleksis/AlekSIS-Core#1483
No description provided.