erdify 0.14.1 — a fix for django-ninja ModelSchema

[FabianClemenz]

erdify 0.14.1 is out 🎉

A patch release, out quickly because it corrects something 0.14.0 got wrong.

ModelSchema no longer renders as an empty entity

0.14.0 added --base-classes, which lets you name a Pydantic base defined outside the scanned files — ninja.Schema, or a shared BaseSchema from an internal library. If you pointed it at ModelSchema, though, you got this:

entity "user" as User {
  primary_key(id) : int
  column(name) : str
}

entity "user_schema" as UserSchema {
  ' (no fields)
}

An empty box beside the real table. django-ninja's ModelSchema (inner Meta) and ninja-schema's (inner Config) take their fields from a Django model rather than from the class body, and erdify does not resolve that reference. An empty entity is worse than no support at all — the diagram stops being incomplete and starts being wrong.

erdify now detects the shape, skips it, and says so:

Warning: skipped UserSchema - its fields come from Meta.model (User), which
  erdify does not resolve. Drawing it would add an entity with no fields.

The Django model itself still renders as usual. Detection is narrow on purpose: only an inner Meta/Config that assigns model counts, so an ordinary Pydantic model with a nested config class — and Django's own class Meta — are untouched.

An open question, if you use these

Resolving those schemas properly is still open in #171, and what blocks it is a design question rather than an engineering one:

Is a response schema an entity, or just a projection of one?

UserSchema mirrors User. Drawing both duplicates the fields and implies a relationship that does not exist. Rendering it only under an opt-in --sources, rendering it as an annotation on the model it projects, or not rendering it at all are all defensible — and they lead to quite different implementations.

If you use ninja.ModelSchema or ninja_schema.ModelSchema: what would you expect to see in the diagram? That answer is the missing piece, not the parsing. #171 is the place for it.

Also in this release

The README and the documentation home page now open with a "five frameworks, one diagram" image — the same User/Order schema written in SQLModel, SQLAlchemy, Django, Pydantic and dataclasses, converging on the ERD they all produce. It reaches PyPI with this release.

---

📦 Release · 📖 Docs · 📝 Changelog