Welcome to Django ORM Lens — v0.3.0 is live, and here's what this space is for

[FROWNINGdev]

Thanks for being here. Django ORM Lens v0.3.0 ships today, and this is the main gathering point for the project. I want to be clear about what different spaces are for so conversations end up in the right place.

What v0.3.0 brings

• CodeLens above every Django model class showing field/relation counts and an "Open ER diagram" action
• ER diagram edge labels: on_delete (CASCADE / SET_NULL / PROTECT) and related_name now surface on every relation
• Theme picker: djangoOrmLens.diagramTheme (auto / default / dark / forest / neutral); auto follows your VS Code color theme
• Python CLI + MCP server — companion package django-orm-lens on PyPI. Zero-dep CLI (scan, describe, hover, list, er) and an optional MCP stdio server exposing five read-only tools to Cursor, Aider, Continue.dev, Zed, and any MCP client.

Full release: https://github.com/FROWNINGdev/django-orm-lens/releases/tag/v0.3.0

What Discussions are for

• Questions about setup, configuration, or how things work
• Ideas for features or directions you'd like to see the project go
• Showing what you've built with the tool — integrations, workflows, use cases
• General feedback that doesn't fit neatly into a bug report
• Anything you want to discuss before opening an issue

What Issues are for

• Confirmed bugs with reproduction steps
• Specific feature requests that are scoped and actionable
• Documentation gaps or errors

If you're not sure which to use, start here. A discussion that turns into a clear bug or feature request can always become an issue later.

A few things I'd especially like to hear about

• How you're using it on large Django projects (lots of apps, lots of models) — that's the use case I want to make bulletproof
• Pain points with the current MCP server integration in your specific AI coding environment
• Anything the ER diagram is getting wrong or missing
• Ideas for how the VS Code extension sidebar could be more useful day-to-day

Contributing

Pull requests are welcome. If you're planning something significant, open a discussion first so we can align before you invest time in it. For small fixes — typos, doc improvements, obvious bugs — just open a PR directly.

Welcome aboard.