Context
Deferred from the --inject design (markdown injection, v0.10.0). The initial implementation supports one marker region per target file (the README 95% case):
<!-- erdify:start -->
```mermaid
erDiagram
...
## Idea (future)
Allow several independent regions in one file — e.g. a per-schema or per-source diagram in different sections of the same doc. Likely needs **named** markers so each `erdify --inject` call targets a specific region:
```markdown
<!-- erdify:start id=auth --> ... <!-- erdify:end id=auth -->
<!-- erdify:start id=billing --> ... <!-- erdify:end id=billing -->
Why deferred (YAGNI)
The common need is a single ERD in the README. Multi-region adds marker-naming syntax, ambiguity rules, and CLI surface (which region + which scope per region) that aren't justified until someone asks. Tracking here so the single-region marker format stays forward-compatible (i.e. don't paint ourselves into a corner — leave room to add an id= attribute later).
Context
Deferred from the
--injectdesign (markdown injection, v0.10.0). The initial implementation supports one marker region per target file (the README 95% case):Why deferred (YAGNI)
The common need is a single ERD in the README. Multi-region adds marker-naming syntax, ambiguity rules, and CLI surface (which region + which scope per region) that aren't justified until someone asks. Tracking here so the single-region marker format stays forward-compatible (i.e. don't paint ourselves into a corner — leave room to add an
id=attribute later).