This allows Django to export JSON-compatible data to the browser. The client-side code accesses the data as a JavaScript object.
Installation
To get the latest stable release from PyPi
pip install django_client_data
Install the app, middleware, and context processor
INSTALLED_APPS = (
...,
'django_client_data',
)
MIDDLEWARE_CLASSES = (
...
'django_client_data.middleware.ClientDataMiddleware',
)
TEMPLATE_CONTEXT_PROCESSORS = (
...
'django_client_data.context_processors.client_data',
)
Usage
Call set_client_data() in your view to export values
from django.views.generic import TemplateView
from django_client_data import set_client_data
class IndexView(TemplateView):
template_name = 'index.html'
def get(self, request, *args, **kwargs):
set_client_data(request, **{'foo': 'bar'})
return super(IndexView, self).get(request, *args, **kwargs)
Include client_data.html in your page
{% include 'django_client_data/client_data.html' %}
The JavaScript object DJANGO.client_data will look like
{
"DEBUG": false,
"STATIC_URL": "/static/",
"csrftoken": "gSlpOPyxHrdQH3KWUEkXx1wfyqGE7MDo",
"foo": "bar",
"url_args": [],
"url_kwargs": {},
"url_name": "index",
"user_full_name": null,
"user_pk": null,
"username": null
}
Settings
CLIENT_DATA_NAMESPACE (defaults to ‘DJANGO’) is the JavaScript global that will be created as the namespace to contain the client data. The data is a property of this global and is named ‘client_data’.
Mechanism
Django Client Data works by attaching a client_data attribute on the request object. The client_data.html template attaches a client_data property to the JavaScript global indicated by CLIENT_DATA_NAMESPACE.
Todo
Add a “context processors” feature to client data so custom values can be injected
Run Tests
./configure.sh
source venv/bin/activate
python django_client_data/tests/manage.py test
Metadata
Release files for django-client-data 0.1.9
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_client_data-0.1.9.tar.gz | 5.6 kB | Without provenance | Details for django_client_data-0.1.9.tar.gz |
Release files / django_client_data-0.1.9.tar.gz
| Download URL | django_client_data-0.1.9.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
650cf67d6938ca8810cfa0e590d8669426dd4529ff4549fed5625cc5939afa4c
|
|
BLAKE2b-256 checksum How to use checksums |
48ba450b47495f20088fb99bbe1951bdc5c0515e4d2082cb59d668d89ac02b21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-client-data 0.1.9
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.