-
-
Notifications
You must be signed in to change notification settings - Fork 145
maximum possible #125
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
maximum possible #125
Conversation
|
Thank you for this. I think another approach would be to create a new form class called |
| @@ -1,54 +0,0 @@ | |||
| *.*~ | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to keep this file :)
You mean, not to have it just as a function, but creating an all new class? Where would that class be? That would mean to have another kind of Question.type to select from? For writing that, I would need more understanding of the code from my part... Some more hints could maybe help me getting there! Thanks! |
|
Yes exactly :) Well we could add the class in https://github.com/Pierre-Sassoulas/django-survey/blob/master/survey/forms.py, then create a Question.SELECT_MULTIPLE_LIMITED value in the Question model, then we need to add this value in all the relevant list like here. The change would be a new class based on SelectMultiple and 3/4 lines of changes for handling a new question type. |
|
I'm trying to inherit that new class from django.forms.widgets.CheckboxSelectMultiple but I do always hit a |
|
Apparently Doc for |
|
Closing in favor of #166 following a rebase. |
First implementation for a field maximum possible answers.
I would like to create a useful notice to the user, so he/she knows why his/her selection was not accepted. At the moment the survey just doesn't get saved. #124