> Swagger has solved that one for years now. I was referring to both the implementation and generating good/complete documentation strings for that, which is

> Swagger has solved that one for years now. I was referring to both the implementation and generating good/complete documentation strings for that, which is tedious and repetitive work. Obviously, I'm using openapi (aka. swagger); support for that is built into fastapi. That's one of the reasons I picked that. The tests are also generated but I screened them manually and iterated on them with chat gpt (also test this, what about that edge case, etc.). I know how to write good tests. But generating them is a way better use of my time than writing them manually. Especially spelling out all the permutations of what can go wrong and should be tested and asserting for that. AIs are better at that sort of thing. These are simple crud endpoint. I've written loads of them over the years. If you are still doing that manually, you are wasting time.