Django-React-Templatetags
This django library allows you to add React (16+) components into your django templates.
Features
- Include react components using django templatetags
- Unlimited amount of components in one view
- Support custom models (that is from the beginning not json-serializable)
- Server side rendering with Hypernova or Hastur
Installation
Install the library with pip:
$ pip install django_react_templatetags
Where to go from here?
You should first read Getting started, then go through these topics:
- Settings
- How to use the templatetags included in this library
- Adding a single component
- Adding multiple components
- Examples
- Working with models
- Server side rendering
- FAQ
Tests
This library include tests, just run python runtests.py
You can also run separate test cases: python runtests.py tests.test_filters.ReactIncludeComponentTest
Coverage
Make sure you have Coverage.py installed, then run coverage run runtests.py to measure coverage. We are currently at 95%.
Contributing
Want to contribute? Awesome. Just send a pull request.
Security
If you believe you have found a security issue with any of our projects please email us at security@frojd.se.
License
Django-React-Templatetags is released under the MIT License.
Metadata
Release files for django-react-templatetags 8.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_react_templatetags-8.0.0.tar.gz | 15.1 kB | Without provenance | Details for django_react_templatetags-8.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_react_templatetags-8.0.0-py3-none-any.whl | Python 3 | none | any | Details for django_react_templatetags-8.0.0-py3-none-any.whl |
Total release size: 36.5 kB
Security for django-react-templatetags 8.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.