2.1.1

Moved the injection of the JSON version into the serializer, rather than the Formidable.to_json() class method. The serializer is called by the method, so it's idempotent (#340).

2.1.0

Main change:

Added the JSON version when going through the Formidable.to_json() class method. This would ensure that stored schemas would carry their version and wouldn't need extra JSON schema migrations (#337).

The Deprecation Wagon

• Deprecate support for Django 1.8 and Django 1.9 (#325).
• Drop crowdin for translation handling (#333).

v1.7.0

Deprecation Warning: Support for django<=1.9 will be dropped by the version 2.0.0.

• Added a tool to build the JSON Schema from the formidable.yml file, and include it into the documentation.
• Add a deprecation warning for django 1.8 and 1.9

1.6.0

This Release 1.6.0 was published on 2018-04-06

• Added compatibility with Python 3.6 (#318).
• Allow change type for the fields without changing name/slug

1.5.2

Release 1.5.2 was committed and tagged on 2018-03-30

• Bugfix: Allow null and empty condition names.
• Other: Added compatibility tests using Django 1.11.

The library was already compatible with Django 1.11, without a code change, so we were lucky. But now we have tests to prove it and eventually get an alert if there's a regression.

1.5.1

Release 1.5.1 was published on 2018-03-28

Change

• Make sure that the ValidateView.form_valid method return an actual empty body content along with a 204 HTTP status response. Before this hotfix, the dictionary passed along as the response content was serialized into a 2-character string to calculate the content-length, but this content was not returned to the client. Some browsers would experience it badly, namely IE11 (#313).

1.5.0

was released on 2018-03-09

• Trim whitespaces in the generated formidable.js file. This is more than just cosmetics, it prevents to have a polluted history on this file (#306).
• Added tests to use conditional rules with drop down lists (#304)
• Added possibility to restrict types of the conditional rules (#304)
• Hotfix: Extract conditions and filter them using the fields that exist in the form (#308).
• Added typing to the demo requirements (#311)
• Make the conditional rule name optional (#307)

[Backport release] Release 1.4.1

Added Hotfix from #308: Extract conditions and filter them using the fields that exist in the form.

[Backport release] Release 1.3.1

Added Hotfix from #308: Extract conditions and filter them using the fields that exist in the form.