List view
The best way to keep your documentation truthful and up-to-date is to have tests for it. We gotta have automated testing for all code snippets in the docs. See how FastAPI and Pydantic approach this.
No due date•2/4 issues closedCadwyn is not really about the framework: it's a language and framework agnostic approach. So it would be wise to modularize cadwyn in a way that would allow us to use it in other frameworks.
No due date•1/1 issues closedCadwyn provides us with a good interface to describe changes between versions for FastAPI and pydantic. But with a little more work we can use the same interface to describe these changes for both internal and external users. This effectively becomes a truthful zero-cost (because you'd do it anyways when making a version) public changelog, which means **a lot** when doing API versioning.
No due date•3/4 issues closedMigrating requests is a huge undertaking as they are much more complex than the usual responses. However, we have to consider them as well if we want universi to be a full-blown solution.
No due date•6/8 issues closed