Documentation: Consider depth of introductory State usage document
It feels weird to me that in an introductory usage document, we effectively say, "Hey, here's a thing you can do with State, but its weird and bug-prone, so don't do it."
Makes me feel that we should have a separate section in usage for State that explores these concepts outside of the app use docs. WDYT?
Originally posted by @peterschutt in #3302 (comment)
litestar-org / litestar
Production-ready, Light, Flexible and Extensible ASGI API framework | Effortlessly Build Performant APIs
5.5k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too