Django-formidable

Latest version: v7.2.0

Safety actively analyzes 688735 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 10

0.9.1

Not secure
==========================

- Use an atomic transaction in FormidableSerialize.save() (220)
- Ensure compatibility with Django REST Framework 3.3 (222)

0.9.0

Not secure
==========================

* Added Django 1.10 support (203).
* Dropped Python 3.3 support (207).
* Fixed the swagger doc generation and rendering (210).
* Fix wrong field type for Checkbox (208).
* Don't rely on database ordering in `NestedListSerializer` (215)
* Provide a tools in order to generate django-form class from json
contextualized definition (171)

0.8.2

Not secure
==========================

* Enforce unicity of keys in NestedListSerializers (202)
* Define __unicode__ and __str__ on models (200)
* Fix regression on presets_lists endpoint (199)

0.8.1

Not secure
==========================

- Fix: Serializers don't allow empty (blank) description on Field and Item (194).

0.8.0

Not secure
==========================

* [ci] Split tox jobs into CircleCI configuration (189).
* Skip form validation rules if a field is empty (191).
* Fix: Confirmation preset validation would correctly compare using the appropriate types (177).
* Change `help_text` to `description` in the API, in order to catch up formidable-ui (188).

0.7.1

Not secure
==========================

* Fix: excluding the `.crowdin` directory in the flake8 tox job (179).
* Return the preview mode (form or table) with the accesses list (121)
* Fix: avoid installing formidable when not needed in tests - flake8 + isort checks (181).
* add presets to ContextFormSerializer (176). Add presets creation directly in a FormidableForm declaration. Rework tests with presets.
* Fix: error message for preset validation is not the one specified (185)
* Improve isort management in tox file (147)

Page 8 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.