v0.14.0

erdify 0.14.0 — ER diagrams for django-ninja schemas, and an honest comparison.

Added

• --base-classes NAME [NAME ...] (and base_classes in [tool.erdify]) names
  extra base classes to treat as Pydantic models. Pydantic detection resolves
  ancestors only across the scanned files, so a base defined in an installed
  package — ninja.Schema from django-ninja — or in an internal library that
  --include does not match was unresolvable, and every subclass of it was
  silently skipped. Both the bare (Schema) and qualified (ninja.Schema)
  forms are matched, and intermediate bases defined in scanned files still
  resolve transitively. Partially addresses
  #171; the
  ModelSchema variants, whose fields come from an inner Meta/Config
  rather than the class body, remain unsupported.

Fixed

• The comparison page and the README comparison table were wrong about two
  rows. Both claimed no alternative ships a Markdown-injection or a CI
  drift-check feature; paracelsus ships
  both, along with [tool.paracelsus] configuration and Mermaid output. It is
  now a column in the comparison table and a named entry under "when to use
  something else": it reaches models by importing them (--import-module), so
  it sees the fully-resolved metadata an AST scan cannot, and for a
  single-SQLAlchemy project that accuracy may be worth more than erdify's
  independence.

---

Install: pip install erdify · Docs: https://erdify.devsuit.io/ · Full diff: v0.13.0...v0.14.0