django-native-jsonform
Build nested, server-validated JSON editors from JSON Schema using ordinary
Django Field, Widget, Form, and ModelForm primitives.
django-native-jsonform is intended for applications that store configurable
data in models.JSONField but still want Django's validation, permissions,
widgets, templates, admin integration, and extension points.
Highlights
- Objects, arrays, nested arrays, choices, local
$ref, and discriminatedoneOfbranches. - Native Django fields and server-side validation—no client-only JSON editor.
- Dynamic schemas with access to the current request, user, object, and form.
- Exact-path,
*, and**overrides for fields, widgets, attributes, serializers, defaults, permissions, and templates. - Cloneable registries for project-specific JSON formats and widgets.
- Sparse JSON preservation: displayed defaults do not have to be persisted.
- Unknown-key preservation for forward-compatible and permission-aware forms.
- Template-driven rendering and small progressive-enhancement JavaScript.
Installation
python -m pip install django-native-jsonform
INSTALLED_APPS = [
# ...
"django_native_jsonform",
]
Quick start
from django import forms
from django_native_jsonform import JSONSchemaFormField, JSONSchemaModelForm
from .models import Product
PRODUCT_SCHEMA = {
"type": "object",
"properties": {
"title": {"type": "string", "title": "Title"},
"price": {"type": "number", "minimum": 0},
"tags": {
"type": "array",
"items": {"type": "string"},
},
},
"required": ["title"],
}
class ProductForm(JSONSchemaModelForm):
metadata = JSONSchemaFormField(schema=PRODUCT_SCHEMA, required=False)
class Meta:
model = Product
fields = "__all__"
For Django admin, add JSONSchemaAdminMixin so callable schemas and factories
receive the current request context:
from django.contrib import admin
from django_native_jsonform import JSONSchemaAdminMixin
@admin.register(Product)
class ProductAdmin(JSONSchemaAdminMixin, admin.ModelAdmin):
form = ProductForm
Customize a project-specific format
from django import forms
from django_native_jsonform import FieldFactoryContext, default_registry
registry = default_registry.clone()
@registry.register_field("string", format="media-asset")
def media_asset_field(context: FieldFactoryContext) -> forms.Field:
return MediaAssetField(
user=context.form_context.user,
schema=context.schema,
required=context.required,
)
class ProductForm(JSONSchemaModelForm):
metadata = JSONSchemaFormField(schema=PRODUCT_SCHEMA, registry=registry)
The package does not depend on a particular rich text editor, media library, autocomplete implementation, or design system. Those are registered by each consumer.
Documentation
The complete wiki lives in docs/ and is published at
barcelona-dev.github.io/django-native-jsonform.
Start with the quick start, then see customization and building extensions.
Status
The API is currently alpha. It was extracted from a production Django
application, but semantic-versioning compatibility begins with 1.0.
License
MIT
Metadata
Release files for django-native-jsonform 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_native_jsonform-0.1.2.tar.gz | 38.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_native_jsonform-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.7 kB
Release files / django_native_jsonform-0.1.2.tar.gz
| Download URL | django_native_jsonform-0.1.2.tar.gz |
|---|---|
| Size | 38.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
322076d6f2ec075c1db52521e993670cc76db6df405f86870a4eb2994948a8cb
|
|
BLAKE2b-256 checksum How to use checksums |
0fccce1f206d6f18b79f503e3a358444122ad29d1ae1f22d4f8b5d33176efaf3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency logRelease files / django_native_jsonform-0.1.2-py3-none-any.whl
| Download URL | django_native_jsonform-0.1.2-py3-none-any.whl |
|---|---|
| Size | 28.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaeff5193de30d6c703f3796fc07d36b89d70f718b55861cc75dd521361f2a21
|
|
BLAKE2b-256 checksum How to use checksums |
e813a9c7e2e1c3ea0fff433d07b9e2b37bb5f5df8c3840590183d260bc20cc4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.
Transparency log