Django-flag-app

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.2.1...v1.3.0>`__

**Features**

- Confirm support for python ``3.10``.

--------------------------------------------------------------------

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.2.0...v1.2.1>`__

**Bug Fixes**

- Fix links for redirecting unauthenticated from flag form to login page.

-----------------------------------------------------------------------------------

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.1.1...v1.2.0>`__


**Features**

- Add link to the related content object in the admin.

- Dropped support for django ``2.1`` (this version is not LTS. See `supported django versions`_ for more information on this).

.. _`supported django versions`: https://www.djangoproject.com/download/#supported-versions

-----------------------------------------------------------------------------------

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.1.0...v1.1.1>`__

**Bug fixes**

- Handle Warning for ``default_app_config`` in django >=3.2.

**Features**

- Move metadata from ``setup.py`` to ``setup.cfg``.
- this means the ``__version__`` string is no longer available. To use the installed versions, you may use ``importlib.metadata.version['django_flag_app']``.

-----------------------------------------------------------------------------------

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.0.1...v1.1.0>`__

**Features**

- Add support for python3.9 and django3.2

-----------------------------------------------------------------------------------

`Full
Changelog <https://github.com/abhiabhi94/django-flag-app/compare/v1.0.0...v1.0.1>`__

**Bug fixes**

- Circular import caused by the use of ``get_user_model`` at modular level in ``flag.managers``.

- Version number according to PEP440