Update README
This commit is contained in:
@@ -35,7 +35,7 @@ Prompt your agent to create a **class diagram** of the classes in `src/Before/`
|
|||||||
|
|
||||||
### Task 2: Sequence diagram — happy path
|
### Task 2: Sequence diagram — happy path
|
||||||
|
|
||||||
Prompt your agent to create a **sequence diagram** for the flow when `Client.FindByName("Jane Doe")` is called. Show the interactions from the call site, through `DbBase.Find<T>()`, to the DbContext lookup, and the result returning.
|
Prompt your agent to create a **sequence diagram** for the flow when `Client.FindByName("Jane Doe")` is called.
|
||||||
|
|
||||||
### Task 3: Sequence diagram — exception path
|
### Task 3: Sequence diagram — exception path
|
||||||
|
|
||||||
@@ -52,6 +52,3 @@ From `Program.cs` (the Console entry point), trace how the database gets initial
|
|||||||
- **Validate:** Use `mmdc` to check syntax, visually check the diagram against the code.
|
- **Validate:** Use `mmdc` to check syntax, visually check the diagram against the code.
|
||||||
- **The skill is directing the agent,** not writing diagrams by hand.
|
- **The skill is directing the agent,** not writing diagrams by hand.
|
||||||
|
|
||||||
## Background
|
|
||||||
|
|
||||||
This is the "before" code from a refactoring exercise (db-subclass-to-dto) where the Active Record pattern is extracted into a DTO + POCO design. The Active Record structure — with its DbContext leak through entity inheritance — is the kind of thing you want to understand before refactoring.
|
|
||||||
|
|||||||
Reference in New Issue
Block a user