Show HN: FastOpenAPI – automated docs for many Python frameworks • Hacker News Board

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#11

Post by mr_Fatalyst » Sat, Mar 22, 2025, 3:08 PM UTC

zapnuk wrote: post #5

Why not just use fastAPI and have it built into the framework?

Sometimes you simply can't switch frameworks—due to legacy code, project constraints, or team preferences. FastOpenAPI is specifically designed for situations like these: it provides FastAPI-style routing and automated OpenAPI docs without forcing you to change the underlying framework.

P.S. I'd prefer FastAPI as well ;)

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#12

Post by Sodosorry » Sat, Mar 22, 2025, 3:09 PM UTC

[flagged]

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#13

Post by mr_Fatalyst » Sat, Mar 22, 2025, 3:10 PM UTC

Onavo wrote: post #10

No love for Django? I am looking for an alternative to DRF and Django-ninja that can optionally generate typed APIs and docs directly from the model definitions.

I actually started working on a router for DRF/Django integration, but Django's project structure made it surprisingly tricky to implement cleanly. It's still on my list though.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#14

Post by mr_Fatalyst » Sat, Mar 22, 2025, 3:14 PM UTC

dtkav wrote: post #7

Nice work! What's your take on spec-first vs. code-first? I'm a fan of spec-first (i worked on connexion), but I've noticed that code-first seems to be more popular.

Thanks! I personally prefer code-first because it aligns well with Python’s dynamic nature and feels more natural in daily coding. Spec-first definitely has advantages (especially clarity and collaboration), but it can sometimes introduce friction, especially when rapidly iterating on APIs.

I think the popularity of code-first tools (like FastAPI) mostly comes from the convenience of quickly defining and changing APIs right alongside your code.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#15

Post by ltbarcly3 » Sat, Mar 22, 2025, 3:16 PM UTC

Every FastApi project I've worked on (more than a few) had an average of less than 1 concurrent request per process. The amount of engineering effort they put into debugging the absolute mess that is async python when it was easily the worst tool for the job is remarkable. If you don't know why it is hilarious that a FastApi project would have less than one concurrent request per process you shouldn't be making technical decisions.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#16

Post by jensenbox » Sat, Mar 22, 2025, 3:17 PM UTC

Onavo wrote: post #10

No love for Django? I am looking for an alternative to DRF and Django-ninja that can optionally generate typed APIs and docs directly from the model definitions.

Why are you looking for an alternative to Django Ninja? What about it is deficient for you? Curious because I am about to use it.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#17

Post by stackskipton » Sat, Mar 22, 2025, 3:18 PM UTC

Onavo wrote: post #10

No love for Django? I am looking for an alternative to DRF and Django-ninja that can optionally generate typed APIs and docs directly from the model definitions.

There is already plenty available that will do what you want. FastAPI or Litestar are two popular ones.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#18

Post by scrollaway » Sat, Mar 22, 2025, 3:19 PM UTC

mr_Fatalyst wrote: post #13

Onavo wrote: post #10

No love for Django? I am looking for an alternative to DRF and Django-ninja that can optionally generate typed APIs and docs directly from the model definitions.

I actually started working on a router for DRF/Django integration, but Django's project structure made it surprisingly tricky to implement cleanly. It's still on my list though.

I believe django-ninja is as good as it gets for this, to be honest. But I wouldn't try to support DRF. Django Ninja implements its own routing and it's a lot better that way.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#19

Post by Onavo » Sat, Mar 22, 2025, 3:20 PM UTC

mr_Fatalyst wrote: post #13

Onavo wrote: post #10

No love for Django? I am looking for an alternative to DRF and Django-ninja that can optionally generate typed APIs and docs directly from the model definitions.

I actually started working on a router for DRF/Django integration, but Django's project structure made it surprisingly tricky to implement cleanly. It's still on my list though.

I would suggest having an option for pure Django integration, without DRF.

Re: Show HN: FastOpenAPI – automated docs for many Python frameworks

#20

Post by Onavo » Sat, Mar 22, 2025, 3:21 PM UTC

scrollaway wrote: post #18

mr_Fatalyst wrote: post #13

Earlier quoted context omitted.

I actually started working on a router for DRF/Django integration, but Django's project structure made it surprisingly tricky to implement cleanly. It's still on my list though.

I believe django-ninja is as good as it gets for this, to be honest. But I wouldn't try to support DRF. Django Ninja implements its own routing and it's a lot better that way.

Django Ninja isn't particularly well maintained, there have been a few attempts at forking already. Also I think the author of Django Ninja is more concerned about surviving the war right now.