Timeline for Is it best practice for each call to a SQL Server to be in its own class, even when using dependency injection?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2023 at 23:56 | comment | added | Flater | @J.Mini Hardcoding the mediator's handlers is the most barebones way of doing a mediator. Look into the Mediatr library for an example on how a mediator can work without requiring you to collect every handler in a god class. Essentially, you develop loose components and Mediatr will connect the dots for you at runtime. | |
| May 25, 2023 at 23:38 | comment | added | J. Mini | It took me many reads before I got your point, so forgive me if I've still missed it. It sounds to me as if your mediator object is just the original huge Data class that I've suggested. I truly see no difference between the two. | |
| May 22, 2023 at 4:25 | history | edited | Flater | CC BY-SA 4.0 | added 731 characters in body |
| May 22, 2023 at 4:11 | history | answered | Flater | CC BY-SA 4.0 |