1.0.0-rc.1

This release has been inspired by Problem Details for HTTP APIs - RFC7807 and
blog post Structuring validation errors in REST APIs
written by @k3nn7.

The main idea has been to simplify validation process on the client side by flattening errors output. To achieve such
a goal, the whole validation process has been rewritten (and luckily for us, much simplified).

• Changed: Positional validation errors for lists
• Changed: ImageField and FileField requires Data URI
  (issue Raise ValidationError in invalid Data URI by default)
• Removed: Form.fill() method replaced by Form.populate()
• Removed: fill_ methods replaced by population strategies

0.21.0

• Feature: Introduced mapping
• Feature: Override strategies using field_type_strategy and field_strategy

0.20.1

• Fix: DictionaryField was unable to raise validation errors for keys

0.20.0

Anniversary release (believe it or not, we are celebrating 2 years already) 🥳

• Feature: Population strategies introduced
• Feature: fill method is deprecated and replaced by populate
• Feature: Settings object introduced (form.settings)
• Feature: Pluggable content-type parsers using DJANGO_API_FORMS_PARSERS setting

0.19.1

• Typing: mime argument in FileField is suppose to be a tuple

0.19.0

• Feature: FieldList and FormFieldList now supports optional min/max constrains using min_length/max_length

0.18.0

• Feature: ModelForm class introduced (experimental, initial support - not recommended for production)

0.17.0

• Feature: fill_method introduced

0.16.4

• Fix: Pillow image object have to be reopened after Image.verify() call in ImageField::to_python

0.16.3

• Fix: ApiFormException('No clean data provided! Try to call is_valid() first.') was incorrectly raised if request payload was empty during Form::fill method call
• Change: clean_data property is by default None instead of empty dictionary