Django-pattern-library

Latest version: v1.2.0

Safety actively analyzes 630094 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 2

0.4.0

Added

- We now officially support Django 3.2, and tentatively Django 4.0 ([144](https://github.com/torchbox/django-pattern-library/pull/144))
- Load templates from template engines’ [`DIRS`](https://docs.djangoproject.com/en/3.2/ref/settings/#dirs) as well as apps’ `templates` subdirectories ([145](https://github.com/torchbox/django-pattern-library/pull/145))

0.3.0

We have a new documentation website! Check out [torchbox.github.io/django-pattern-library](https://torchbox.github.io/django-pattern-library/).

Added

- This package now supports Django 3.1, and has tentative support for Django 3.2
- We also now support Python 3.9
- Implement optional default for [override_tag](https://torchbox.github.io/django-pattern-library/reference/api/#override_tag) ([125](https://github.com/torchbox/django-pattern-library/issues/125))
- A new `render_patterns` command makes it possible to export the pattern library templates for automated tests or static hosting ([16](https://github.com/torchbox/django-pattern-library/issues/16), [#17](https://github.com/torchbox/django-pattern-library/issues/17))
- Permit variable template names in extends and include tags ([112](https://github.com/torchbox/django-pattern-library/pull/112))

Removed

- We no longer support Django 1.11, 2.0, 2.1
- The project no longer includes polyfills for all ES6 features, and only supports modern browsers.

Fixed

- Pages and fragments are now handled correctly again ([119](https://github.com/torchbox/django-pattern-library/issues/119))
- PyPI package metadata now uses absolute URLs to GitHub ([120](https://github.com/torchbox/django-pattern-library/issues/120)).

Page 2 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.