Type hints in model fields prevents proper operation

[jsabater]

VS Code version

VSCodium 1.126.04524

OS

Ubuntu 24.04 (Tuxedo OS)

Steps to reproduce

1. Open Django 6 project with Django Ninja 1.6.2.
2. Visit the Django ORM Lens. It renders the tree and the preview works correctly.
3. Add a type hint to the first field of the first model in a file.
4. Save the change. The field disappears from the tree.
5. Open the graphical preview, the field is not there.
6. Keep doing that to other fields, the entity ends up empty in the preview and the tree.

Sample models.py (minimized)

class RevokedToken(models.Model):
    """A revoked JWT, keyed by its ``jti`` claim (the token denylist)."""

    jti: CharField[str] = models.CharField(max_length=32, unique=True)
    ...

[FROWNINGdev]

Confirmed the reproduction and fixed in v0.7.3 / py-1.2.3 (just published).

Root cause: FIELD_RE / BARE_FIELD_RE expected name = models.X( with nothing between the name and =. When you added a PEP-526 annotation the regex silently failed, no field parsed, entity ended up empty in the tree and preview — exact reproduction you described.

Fix: added an optional (?:\s*:[^=]+)? group between the field name and = in both parsers (Python + TypeScript). Applied consistently to FIELD_RE, BARE_FIELD_RE, and META_ITEM_RE. [^=]+ is safe because = never appears inside a Python type expression (subscripts, unions, dotted refs, generics all use other punctuation).

Pinned with 7 new regression tests using your exact snippet plus a few variants (bare-import form IntegerField[int] = IntegerField(...), plain label: str = ... non-generic annotation, Meta block with annotated attribute ordering: list[str] = [...], plus untyped backward-compat).

Update paths:

pip install --upgrade django-orm-lens                            # CLI + MCP
code --install-extension frowningdev.django-orm-lens             # VS Code
codium --install-extension frowningdev.django-orm-lens           # VSCodium (Open VSX)

The VSCodium extension is at v0.7.3 on Open VSX — should reach you within a few minutes after auto-publish finishes. Thanks a lot for the clean repro against a real Ninja 1.6 codebase — that's the exact kind of report that catches the highest-value bugs.