Django json field empowered by pydantic
Project description
Django Structured JSON Field
This is a Django field that allows you to declare the structure of a JSON field and validate it.
Features
- Define the structure of a JSON field using Pydantic models
- Validate the JSON field against the defined structure
- Use relationships between models inside the JSON field 🤯
- Easily integrate with Django Rest Framework serializers
- Admin editor for the JSON field with autocomplete search for related models 👀
Installation
pip install django-structured-json-field
Usage
from django.db import models
from structured.fields import StructuredJSONField
from structured.pydantic.models import BaseModel
# Define this schema as you would do with a Pydantic model
class MySchema(BaseModel):
name: str
age: int = None
def init_data():
return MySchema(name='')
# Create a model with a StructuredJSONField with the schema you defined
class MyModel(models.Model):
structured_data = StructuredJSONField(schema=MySchema, default=init_data)
Relationships
This field supports relationships between models, you can define them in your schema and they will be treated as normal django relationships. It also supports recursive schemas.
Recursion
You can define recursive schemas by declaring the attribute type as a string:
from typing import Optional, List
class MySchema(BaseModel):
name: str
age: int = None
parent: Optional['MySchema'] = None
relateds: List['MySchema'] = []
Foreign Keys
You can also define model relationships in your schema:
from structured.pydantic.fields import ForeignKey
class MySchema(BaseModel):
name: str
age: int = None
fk_field: ForeignKey['MyModel'] = None
This will treat the parent field as a normal django ForeignKey.
Tip:
You can omit the ForeignKey
field and just use the model class as the type annotation:
class MySchema(BaseModel):
name: str
age: int = None
fk_field: MyModel = None
the field will still be treated as a ForeignKey if the type annotation is a subclass of django models.Model
.
ManyToMany
If you need a ManyToMany relationship, you can use the QuerySet
field:
from structured.pydantic.fields import QuerySet
class MySchema(BaseModel):
name: str
age: int = None
parents: QuerySet['MyModel']
QuerySet
fields will generate a django object manager that will allow you to query the related objects as you would do with a normal django QuerySet
.
instance = MySchema(name='test', age=10, parents=MyModel.objects.all())
# You can filter the queryset
instance.parents.filter(name='test')
# You can count the queryset
instance.parents.count()
# You can get the first element of the queryset, etc...
instance.parents.first()
Admin integration
The field is integrated with the Django admin, you can use the autocomplete search to select the related models. To allow the autocomplete search you need to include structured.urls in your urls.py file:
from django.urls import path, include
urlpatterns = [
path('admin/', admin.site.urls),
path('', include('structured.urls')),
]
Rest Framework integration
You can easily integrate structured fields with Django Rest Framework serializers, just use the StructuredModelSerializer
as the base class for your serializer:
from rest_framework import serializers
from structured.contrib.rest_framework import StructuredModelSerializer
class MyModelSerializer(StructuredModelSerializer):
class Meta:
model = MyModel
fields = '__all__'
Errors generated by pydantic validation will be automatically translated to DRF errors.
Cache
To prevent the field from making multiple identical queries a caching technique is used. The cache is still a work in progress, please open an issue if you find any problem. Actually the cache covers all the relations inside a StructuredJSONField, optimizing the queries during the serialization process.
Cache engine progress:
- Shared cache between
ForeignKey
fields andQuerySet
fields - Shared cache through nested schemas
- Shared cache through nested lists of schemas
- Shared cache between all
StructuredJSONFields
in the same instance - Shared cache between multiple instances of the same model
- Cache invalidation mechanism
Settings
You can manage structured field behaviour modifying the STRUCTURED_FIELD
setting in your settings.py
file. Here a list of the available settings and their default values:
STRUCTURED_FIELD = {
'CACHE':{
'ENABLED': True,
'SHARED': False # ⚠️ EXPERIMENTAL: this enables a thread-shared cache, it's not recommended to use it in production.
},
}
Contributing
The project is open to contributions, just open an issue or a PR.
Running tests
pip install -r requirements-dev.txt
make test
Running test app
pip install -r requirements-dev.txt
python manage.py migrate
python manage.py runserver
License
This project is licensed under the MIT License - see the LICENSE file for details
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
Built Distribution
File details
Details for the file django_structured_json_field-0.2.0.tar.gz
.
File metadata
- Download URL: django_structured_json_field-0.2.0.tar.gz
- Upload date:
- Size: 1.9 MB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/5.1.1 CPython/3.12.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | df5065b06ca7d9d1993b80cdff073b8354383d999fede072ac803cedc1814829 |
|
MD5 | 28214e27063c5814564884b8252101fd |
|
BLAKE2b-256 | bab672b14c404640f776bf916078f830f307b3859ee14af304f9a1a2b86e41ad |
File details
Details for the file django_structured_json_field-0.2.0-py2.py3-none-any.whl
.
File metadata
- Download URL: django_structured_json_field-0.2.0-py2.py3-none-any.whl
- Upload date:
- Size: 1.9 MB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/5.1.1 CPython/3.12.7
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 03100eb5081185680d257349b0aab0299dbd588c68305fe5a4b59f8ed53c908e |
|
MD5 | 130ce8dfe345b51fef7fc2e26b3e3314 |
|
BLAKE2b-256 | c694a14b6f0995889fe8efa08f4308a176f01e5ff6fee34b928484e2bfb3c75c |