django-formidable
django-formidable copied to clipboard
On the way to glory! again!
Follow-up of #188 ## TODO * [ ] Migration: `Field.help_text` → `Field.description` * [ ] Migration: `Item.help_text` → `Item.description` * [ ] Make sure that schema already serialized are still...
Through the API the input data are serialized into the final formidable object. When a formidable object is deserialized, the API re-generated again the json schema. The main idea is...
In the context of the builder, if you add a "checkboxes" field, it appears that the front-end may or may not send us the "multiple" property. If not, when we...
As the [Django documentation suggests](https://docs.djangoproject.com/en/1.11/ref/forms/validation/#raising-validationerror), Django ``ValidationError``s exceptions should > Provide a descriptive error code to the constructor This was a "django-only" feature, and was not compatible with DRF errors...
I would like to : - cache the results of `get_migrations` - be able to get the current version of the JSON Formidable schema
As an integrator of the django-formidable module, I'd like to know how to handle the permissions, what is my options to allow/reject a resource access. The ``FORMIDABLE_DEFAULT_PERMISSION``, ``FORMIDABLE_PERMISSION_USING`` and the...
What is the data in form serialization? What is the data in the update request ? ping @moumoutte @wo0dyn
Définir des champs required/disabled dans l'API Crud ( égalemen dans les modèles par extension)