Skip to content

v1.0.3 — empty overview diagram on dbt import

Choose a tag to compare

View all tags
@KKranthi6881 KKranthi6881 released this 21 Apr 22:24
· 182 commits to main since this release
v1.0.3
53f52ee
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release — fixes the post-dbt-import landing UX so users see a clean "build your first diagram" canvas instead of a dbt sources file rendered as if it were a real diagram.

Install

```bash
pip install --upgrade datalex-cli
```

What changed

Before: importing a dbt project auto-opened whichever source file parsed first (e.g. `models/staging/ecom.yml` with a `kind: source` block listing 6 raw tables), showing those entries on the canvas as a fake diagram titled "raw" with 0 relationships.

After: `/api/dbt/import` seeds `datalex/diagrams/overview.diagram.yaml` (`entities: []`) when the import didn't produce its own `.diagram.yaml`, and both frontend loaders open that diagram first. The canvas opens genuinely empty with the Add Entities CTA. Source files like `ecom.yml` remain clickable in the Explorer for users who want to see their dbt sources — just not as the default landing.

Fixed

  • Landing UX: clean empty overview instead of auto-opening a sources file
  • `.diagram.yaml` extension preserved through the edit-in-place path-rewrite (previously `.yaml → .yml` was unconditional and would have renamed diagram files to `.diagram.yml`)
  • Disk seeding in edit-in-place mode: the overview diagram is persisted alongside the other imported YAMLs so it survives a page refresh

See CHANGELOG.md for full details.

Assets 2
Loading