A few little helpers.
Instead of this:
def view(request):
context_dict = {'items': MyModel.objects.all()}
return render(request, "template.html", context_dict)
Use this:
from ajaxify import render_ajax
def view(request):
context_dict = {'items': MyModel.objects.all()}
return render_ajax(request, "template.html", template_fragment.html", context_dict)
Now if your view is responding to AJAX requests it will respond with only the generated fragment.
1 maintainer
Metadata
1 maintainer
Release files for django-ajaxify 0.0.1
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 | |
|---|---|---|---|---|
| django-ajaxify-0.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Release files / django-ajaxify-0.0.1.tar.gz
| Download URL | django-ajaxify-0.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e53bf17e1d87165578aaeab38986b69e53cbadbd647725a93c63743cf18388f8
|
|
BLAKE2b-256 checksum How to use checksums |
874d3a2c36b3414ff5ce8364472a5966b9cdbf5248febb26a5e0e0c61a29d445
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-ajaxify 0.0.1
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.
