Skip to main content

Edit JSON field using Django Model Form

Project description

django-entangled

Edit JSON-Model Fields using a Standard Django Form.

Use-Case

A Django Model may contain JSON fields. Django itself, provides a JSON field specific to Postgres. For other database implementations, there are plenty of alternatives.

Typically, the widget to edit a JSON field is a <textarea ...><textarea>. This HTML element however is very inpracticable for editing. One possibility is to use a generic JSON editor. This however prevents to use all the nice form validation features provided by Django forms. By using django-entangled, one can use a slightly modifed Django ModelForm, and store all or a subset of that form fields inside one or more JSON fields.

Installation

Simply install this Django app, for instance using:

pip install django-entangled

There is not need to add any configurations directives to the project's settings.py.

Example

Say, we have a Django model to describe a bunch of different products. Some fields are used by all products, whereas others describe the properties of that product. Since we don't want to create a different product model for each product type, we use a JSON field to store these arbitrary properties.

from django.db import models
from django.contrib.postgres.fields import JSONField

class Product(models.Model):
    name = models.CharField(max_length=50)

    price = models.DecimalField(max_digits=5, decimal_places=2)
    
    properties = JSONField()

In a typical form editing view, we would create a form inheriting from ModelForm and refer to this model using the model attribute in the Meta-class. Here the properties-field would show up as unstructured JSON rendered inside a <textarea ...><textarea>. This definitely is not what we want! Instead we create a typical form using the special mixin class EntangledModelFormMixin.

from django.forms import fields, models
from entangled.forms import EntangledModelFormMixin
from .models import Product

class ProductForm(EntangledModelFormMixin, models.ModelForm):
    color = fields.RegexField(
        regex=r'^#[0-9a-f]{6}$',
    )

    size = fields.ChoiceField(
        choices=[('s', "small"), ('m', "medium"), ('l', "large"), ('xl', "extra large")],
    )

    class Meta:
        model = Product
        fields = ['name', 'price']
        entangled_fields = {'properties': ['color', 'size']}

In addition to the mixin class EntangledModelFormMixin we add a special dictionary named entangled_fields to our Meta-options. The key (here 'properties') in this dictionary refers to the JSON-field of our model. The value (here ['color', 'size']) is a list of named form fields, declared in our form- or base-class of therefore. This allows us, to assign standard Django form fields to arbitrary JSON fields declared in our Django model.

We can use this form in any Django detail view. A typical use-case, is the built-in Django ModelAdmin:

from django.contrib import admin
from .models import Product
from .forms import ProductForm

@admin.register(Product)
class ProductAdmin(admin.ModelAdmin):
    form = ProductForm

Since the form used by this ModelAdmin-class can not be created dynamically, we have to declare it explicitly using the form-attribute. This is the only change which has to be performed, in order to store arbitrary content inside our JSON model-fields.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-entangled-0.1.tar.gz (6.7 kB view details)

Uploaded Source

File details

Details for the file django-entangled-0.1.tar.gz.

File metadata

  • Download URL: django-entangled-0.1.tar.gz
  • Upload date:
  • Size: 6.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.9.0 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.6

File hashes

Hashes for django-entangled-0.1.tar.gz
Algorithm Hash digest
SHA256 4cc39273655c7a64ea10ed4478fbefc0b5fabb999019b47d387d81c84765d6ce
MD5 a6b4bb45a0ee24b55d03e6e19af05523
BLAKE2b-256 752e481e6fc57df7491034585b5e1a4107e1019a23915b632cf45064ba521337

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page