With FastAPI we get the OpenAPI specification and the Swagger interactive documentation for free. While that is a great help, the automatically generated documentation is not always as helpful as it could be. Let us look for ways in which we can fine-tune the documentation. This post is part of my journey to learn Python. …
With the T4.FileManager we got the missing part to create a code generator based on T4 templates that puts classes into their own files. With that problem solved, we can start our automation project and generate classes for all our database tables, generate the repositories to access the data and finish with integration tests to …
While improving the HTTP status codes, I noticed that there should be a header pointing to the newly created task. Let us add that header to our FastAPI application. This post is part of my journey to learn Python. You find the code for this post in my PythonFriday repository on GitHub. Extend the …
When we generate code with T4, we end up with one single output file per template. That works if we only generate one HTML page or a single class. But when we want to generate multiple classes, the single output file is annoying. We never would let the developers write code that way; therefore, we …
Our to-do application currently responds with the HTTP status codes 200 when everything is ok and 404 if the requested task does not exist. While this works, it is not as specific as it could be. Let us explore our options when it comes to HTTP status codes. This post is part of my journey …
After exploring the theoretical side of an automation project over the last few weeks, it is now time to get our hands dirty and write some code. There are many options for code generation, but I prefer the T4 templates. We have been using them for years and they are so stable that they form …
The basic models we used for our tasks are good to make sure we get the right types. However, if we accept something like int or string, we could get enormously large inputs that are valid strings or numbers but make no sense at all for our application. Let us explore ways to limit our …
When we settled with a standardised approach on how to do the work and we simplified it as much as possible, we can finally enter the phase of automation. In this last phase we face a new set of challenges that may left you baffled. Let us explore the traps so that we know what …
The to-do application started nicely and with the refactoring we got the most obvious code smells fixed. While checking the API in uvicorn, I noticed three missing features that we are going to implement in this post. This post is part of my journey to learn Python. You find the code for this post in …
Before we dive into making the work as simple as possible, we should have decided on the one way we want to do the work. Make sure that everyone is on the same page, otherwise you will need to repeat the simplification step for every variation of the not yet standardised approach! Prepare for …