Skip to content

Commit 18c6c7d

Browse files
dkattanCopilot
andcommitted
docs: describe same-project generated contract analysis
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent e1745d5 commit 18c6c7d

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

‎docs/topics/dto-shapes-and-read-models.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,3 +63,9 @@ This is the layer that makes richer read DTOs practical without forcing every re
6363
Generated contract shapes are not limited to a single nullability policy. A single source type can now describe stricter read-facing contracts and more permissive write- or patch-facing contracts from the same model.
6464

6565
That keeps generated interfaces and DTO classes aligned with their actual API semantics instead of forcing one nullability story onto every generated output.
66+
67+
## Same-project generated contracts are available during analysis
68+
69+
When generated contract shapes target the same project that declares the source type, Coalesce now materializes those generated contracts early enough for analysis and validation to see them consistently.
70+
71+
That keeps same-project generated interfaces and classes usable without introducing duplicate-member diagnostics or forcing consumers to move those shapes into a different project.

0 commit comments

Comments
 (0)