It's been running great inside Takahē for over a week, so I have extracted Hatchway, my new Django API framework, into its own project: https://github.com/andrewgodwin/django-hatchway

In short - it uses type annotations for everything, and it uses standard URL patterns, as these were the things that I couldn't find elsewhere.

GitHub - andrewgodwin/django-hatchway: An unsurprising Django API framework

An unsurprising Django API framework. Contribute to andrewgodwin/django-hatchway development by creating an account on GitHub.

GitHub
@andrew You made this as an alternative to django-ninja? I thought I saw takehe using that when I checked out the code, and thought it was a neat idea, and this seems like it would be solving a similar kind of problem.
@mrchrisadams I did - I quite like ninja, but not the separate API router, and I needed the ability to say some arguments from either GET _or_ POST
@andrew Neat! Any plans on doing the same for stator?
@valberg Totally, but that will take more work to extract due to the models and management command side
@andrew Awesome! Looked through it some time ago and it very much aligns with the way we do stuff with Celery at work. There we just have a beat task for each model that needs to be processed. Stator feels like more of a "djangoesque" way of doing it.
@andrew QueryOrBody is nice. I wish fastapi supported that, however it would make it more complicated to represent in an openapi schema, and makes it harder to validate inputs as well
@benfalk Yeah, this is somewhat done out of necessity because the Mastodon API works this way. When I do OpenAPI generation, I'll figure something out.