ExerciseTracker.TwilightSaw

[TwilightSaw]

No description provided.

[chrisjamiecarter]

Hey @TwilightSaw 👋,

Excellent work on your ExerciseTracker project submission 🎉!
I have performed a peer review and have added some praise and suggestions as bespoke comments.

---

I will go ahead and mark as approved, keep up the excellent work on the next projects! 😊

Best regards,
@chrisjamiecarter 👍

[chrisjamiecarter]

🟠 Optimizing for a Dependency Injection Framework

💡 In a modern DI setup, you would typically register services with the DI container in a ConfigureServices method or equivalent during application startup. For example:

services.AddDbContext<AppDbContext>(options => 
    options.UseSqlServer(configuration.GetConnectionString("DefaultConnection")));

services.AddScoped<IExerciseRepository<Exercise>, ExerciseRepository<Exercise>>();
services.AddScoped<IExerciseService, ExerciseService>();
services.AddScoped<IExerciseDapperRepository<Exercise>, ExerciseDapperRepository<Exercise>>();
services.AddScoped<IExerciseController, ExerciseController>();

Then resolve the top-level service (Menu) through the DI container:

using var scope = app.Services.CreateScope();
var menu = scope.ServiceProvider.GetRequiredService<Menu>();
menu.AddMenu();

This approach:

• Removes the need for manual dependency management.
• Promotes scalability and testability.
• Simplifies code by letting the DI container handle lifecycle management.