PharmaStock Development Blog

 I completed the full Medication API (GET, POST, PUT, PATCH, DELETE) and finished SCRUM-37, implementing the stock quantity adjustment endpoint. Inventory quantities can now be increased or decreased, negative values are prevented, and all changes persist correctly in the database. I also finalized the inventory creation flow with duplicate lot validation and verified everything through Swagger testing. On the frontend side, I started SCRUM-38 and began building the Angular inventory list component to connect the UI to the new backend functionality. Overall, this week solidified the backend foundation and began transitioning into full-stack development. Medication Post Workflow            Medication Post          Post Inventory for new medication               Inventory adjustments

 This week was mainly about making sure the backend database is solid and working the way it should. I focused on validating the DbContext, checking migrations, and confirming that our schema is properly aligned with the development branch. As part of that process, I helped with merging the ASP.NET Core Identity changes and then rebuilt the database from scratch using Docker. Doing a full reset made sure there were no leftover migration issues or hidden conflicts. After rebuilding, I verified that: Identity tables were created correctly Medications has the correct unique index InventoryStocks enforces the foreign key relationship Seed data loaded successfully (10 medications, 11 stock records) No big new features this week just making sure the foundation is clean and stable so we can keep building without surprises later.

 This week marked the transition from planning and design into real backend development. After organizing the project structure and defining use cases in previous weeks, I focused on building the technical foundation that the rest of the application will depend on. The primary goal was completing SCRUM-16, which involved connecting the ASP.NET Core backend API to a MySQL database and verifying that the system could successfully generate and manage database tables. I began by configuring MySQL to run inside a Docker container. Using Docker ensures that every developer on the team works against the same database environment, which reduces setup inconsistencies and avoids the common “it works on my machine” problem. Once the container was running correctly, I verified that it could be started, stopped, and inspected reliably. Next, I integrated Entity Framework Core with the Pomelo MySQL provider and registered the DbContext within the application. This step allows the backend to m...