Postgresql Selects for Update

Release 3.2.0 was released on 2019-11-07

• Extend the test matrix to spread through different DRF versions.
• Drop support for Django 1.10 (EOL was in December 2nd, 2017).
• Launch tests on Postgresql as well as SQLite. Launching these tests will be possible both locally and on Circle-CI. See the "dev" documentation on how you can run tests on your development environment (#161).
• Add select_for_update() on selection in querysets when the Form is about to be modified (namely PUT & PATCH views). This could prevent Database deadlocks when several changes are attempted on the same large form.
• Upgrade to swagger-ui 3.23.11 (#371 & #367).

En route to DRF 3.9.x

Released on 2019-06-03

Fixes

• Fix documentation build (#363).
• Upgrade requirements to Django REST Framework 3.9.x.

3.0.1

• Clean up help_text migration (#292)
• Freeze perf-rec version for the python 2.7

v3.0.0 - Happy Halloween!

Released on October 31st, 2018 (Happy Halloween)

Main Changes

• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields (#345).
• Extend the validation in the filler API to allow validation of extra fields (#348).
• Refactoring of the field builder (Use only one module for the form builder factory) (#347).
• Add parameters to the fields schema.
• Allow Fields and Widgets to introduce parameters when being stored as Formidable models instances (#358).
• Added pytz as a requirement.
• Enforce support for Django REST Framework to the version 3.8.x ; the 3.9 series is incompatible with our current codebase.

Minor Changes

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).
• Skip tox installation in the circle-ci environment: it's already there (#344).

3.0.0rc5

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields (#345).
• Extend the validation in the filler API to allow validation of extra fields (#348).
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).
• Skip tox installation in the circle-ci environment: it's already there (#344).
• Refactoring of the field builder (Use only one module for the form builder factory) (#347).
• Add parameters to the fields schema.
• Allow Fields and Widgets to introduce parameters when being stored as Formidable models instances (#358).

3.0.0rc4

Main Changes

• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields (#345).
• Extend the validation in the filler API to allow validation of extra fields (#348).
• Refactoring of the field builder (Use only one module for the form builder factory) (#347).
• Add parameters to the fields schema

warning: The plugin mechanism is on BETA mode, and at the moment, it only allows to define business-logic fields at "form building time". It means there's not business-logic validation mechanism when you're filling a form previously defined with your custom field.
This is a work in progress, please bear with us.

Minor changes

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).
• Skip tox installation in the circle-ci environment: it's already there (#344).

3.0.0rc3

Main Changes

• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields (#345).
• Extend the validation in the filler API to allow validation of extra fields (#348).
• Refactoring of the field builder (Use only one module for the form builder factory) (#347).

warning: The plugin mechanism is on BETA mode, and at the moment, it only allows to define business-logic fields at "form building time". It means there's not business-logic validation mechanism when you're filling a form previously defined with your custom field.
This is a work in progress, please bear with us.

Minor changes

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Skip tox installation in the circle-ci environment: it's already there (#344).
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).

3.0.0rc2

Main changes

• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields.
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).

warning: The plugin mechanism is on BETA mode, and at the moment, it only allows to define business-logic fields at "form building time". It means there's not business-logic validation mechanism when you're filling a form previously defined with your custom field.
This is a work in progress, please bear with us.

Minor changes

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Skip tox installation in the circle-ci environment: it's already there (#344).
• Refactoring of the field builder (Use only one module for the form builder factory) (#347).

v2.1.2

Hotfix change

• Django field disabled option are now set through the field builder (#351).

v3.0.0rc1

Main changes

• Added a plugin mechanism, allowing users to define and integrate their own "business logic" fields.
• Change the global exception handling error level, from "error" to "exception". It'll provide better insights if you're using Logmatic or any other logging aggregator (#336).

warning: The plugin mechanism is on BETA mode, and at the moment, it only allows to define business-logic fields at "form building time". It means there's not business-logic validation mechanism when you're filling a form previously defined with your custom field.
This is a work in progress, please bear with us.

Minor changes

• Upgrade to Circle-CI 2 (before the end of life of Circle-CI v1 on August, 31st 2018). (#342)
• Optimize Circle-CI usage by using the tox matrix in tests (#343)
• Skip tox installation in the circle-ci environment: it's already there (#344).