-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boolean field always ask for true value #22
Comments
Obviously, please set |
actually, I'm aware that you can set required=false; however the example project does not accept the boolean field unless its value entered is true, making the example project not functioning correctly unless the user edits the project. |
Ah, that sounds legit. |
I have a similar issue. Boolean fields always require to be ticked for the form to submit. In the code I discovered this:
Removing the Meta completely fixes the issue because I can decide on my own if the field is required to be ticked or can be left blank. Now I don't really understand why that exclude was added and would suggest to remove it. |
Do you want to provide a pull request + patch for that? Happy to review it 😄 |
after thinking about a use case; I think it's right the way it's right now. Example, a form may have boolean at end of the form for the following question check here X to accept the agreement; the checkbox must be True for the form to be submitted successfully, therefore, in this case, the developer sets this booleanfield as required. and it should only be accepted if it's value is True, the same as current behavior |
When I create a boolean field, it will not accept the form unless I set it to TRUE.
The text was updated successfully, but these errors were encountered: