-
Notifications
You must be signed in to change notification settings - Fork 4
Plugin mechanism #345
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
Plugin mechanism #345
Conversation
syldb
left a comment
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.
LGTM
| help_text = models.TextField(null=True, blank=True) | ||
| multiple = models.BooleanField(default=False) | ||
| order = models.IntegerField() | ||
| parameters = JSONField(null=True, blank=True, default={}) |
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.
Why do we need blank and null while there is a default value?
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.
It's a habit for the Django models. When you use it from the admin panel, you can't save a blank field if you haven't specified null=True, blank=True even with a declared default value. Maybe it's an overkill here but I'd like to keep it.
4c5a747 to
c141b47
Compare
| model_name='field', | ||
| name='parameters', | ||
| field=jsonfield.fields.JSONField( | ||
| blank=True, default={}, null=True |
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.
I think that the best would be to merge this migration with the 0009, and keep its "semantic" name, instead of the automatically generated one.
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.
Ok for me, do you want to do it?
syldb
left a comment
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.
LGTM
…lds that go beyond the classical / usual fields available in `django-formidable`. * Added a documentation on how to create a new external field module, * Added a new field in the models to carry the parameters. By default, this field is not (de)serialized, you'll need to activate it by hand as explained in the docs and handle its validation by yourself.
it in the field serializer
e750345 to
4aa3835
Compare
|
@brunobord do you have some other suggestions? |
brunobord
left a comment
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.
LGTM. I'll add a warning in the RC changelog about the fact that only the builder is integrated.
Review
This PR closes #
formidable.ymlfile: runtox -e swagger-staticsto rebuild the swagger static files and commit the diff.CHANGELOG.rstUpdated