Django Google Optimize Versions Save

• Bump dependencies
• Run tests for django 3.1

Changes:

• Use get() instead of accessing by key in-case the cookie gets deleted

Changes:

• Return an empty object instead of none when failing to parse cookies or settings. Removes necessity of checking the google_optimize object

Changes:

• Remove logging when no experiment is added

Changes:

• Use a model to manage and interact with the Google Experiment via the Django admin panel
• Add an experiment cookie model for managing the current active experiment while developing via the Django admin panel
• Add a model to manage the experiment variants via the Django admin panel
• Remove configuration management from settings.py

Breaking:

• Removed configuration management from settings.py

Check out the updated documentation.

https://pypi.org/project/django-google-optimize/0.1.9/

Breaking:

• Context processors are removed and a middleware has been added. This is due to context processors not being accessible in the views.

Read the updated docs to understand how to set up the middleware.

https://pypi.org/manage/project/django-google-optimize/release/0.1.8/

Breaking:

• Folder renamed to django_google_optimize from google_optimize, ensure you import django_google_optimize instead of google_optimize.

Major change:

• Tox and pyproject/poetry for project management

https://pypi.org/manage/project/django-google-optimize/release/0.1.7/

Fetch A/B version based on:

• Context processor

Simplifies usage with templatetags.

https://pypi.org/project/django-google-optimize/0.1.4/