I've upgraded Django to 3.2, fixed the deprecation warning, and ran tests.
I didn't change anything in the library itself, but had to make a few minor adjustments to the tests:
Django 3.2:
> ./manage.py test
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
.....................................................
----------------------------------------------------------------------
Ran 53 tests in 0.130s
OK
Destroying test database for alias 'default'...
Django 3.1:
> ./manage.py test
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
.....................................................
----------------------------------------------------------------------
Ran 53 tests in 0.134s
OK
Destroying test database for alias 'default'...
Django 2.2:
> ./manage.py test
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
.....................................................
----------------------------------------------------------------------
Ran 53 tests in 0.127s
OK
Destroying test database for alias 'default'...
Related to https://github.com/rsinger86/drf-flex-fields/issues/82.
I've upgraded Django to 3.2, fixed the deprecation warning, and ran tests. I didn't change anything in the library itself, but had to make a few minor adjustments to the tests:
Django 3.2:
Django 3.1:
Django 2.2: