The time has finally come. You are probably eager to fix some of the issues we saw in chapters 3 and 4, and now we’ll get to do that. First things first, let’s come up with a game plan on how to tackle this refactoring. We already know a couple of things that we need to do differently:
- In chapter 3 we were told to use .NET 5 instead of the .NET Framework for the new version of the Flying Dutchman Airlines service.
- We need to rewrite the endpoints to be clean code (in particular, adhering to the DRY principle).
- We need to fix the security vulnerability—a hardcoded connection string.
- The object names do not match the database column names. We should fix that to ensure a perfect isomorphic relationship between the codebase and the database.
- We need to adhere to the OpenAPI file discussed in chapter 3 and shown in appendix D.