How andrew-paes/money-maker works
Project type and purpose
• This is a backend‐focused, layered, C#/.NET Web API (“Money Maker”) used to offer investment products, let users register, purchase, contribute to products and view transactions & returns. There is no SPA or server‐rendered UI in this repo—this lives purely as a RESTful service with a SQL database.
File structure
• Top‐level “src/Money.Maker” solution with four projects:
a. Money.Maker.Api – the Web API hosts controllers and middleware (Startup.cs/Program.cs).
b. Money.Maker.Domain – domain/data models and response models.
c. Money.Maker.Repository – EF Core DbContext, migrations, repository interfaces & implementations.
d. Money.Maker.Service – business logic through service interfaces & implementations.
• A Test project (Money.Maker.Test) holds basic unit tests.
• SQL folder with seed script; Postman collection for API testing.
• Configuration files (appsettings.json + Development override) and EF Core Migrations in the Repository project.
Key README insights
• Confirms purpose: display investment products, user registration, acquisitions, contributions, and viewing transactions.
• Uses a SQL database (seed.sql) and provides a Postman collection for manual API verification.
Essential details to capture
• Startup.cs DI configuration linking interfaces to implementations.
• EF Core migrations generating schema.
• DataModels in Domain project (Address, City, Customer, etc.).
• ResponseModels for shaping API output.
• Utility classes (e.g., ServiceExtensions, DataSettings).