Tools: Released — Schema Support, Cleaner Internals & What’s Next

✨ What’s New in This Release ## ✅ Schema Support (Big One) ## 🧹 Code Quality Improvements ## 🗄️ Storage: In-Memory + SQLAlchemy (Optional) ## 🧠 What We’re Improving Next ## 🔍 Better Test Coverage ## 🧩 Clear Storage Abstraction ## 📚 Better Documentation & Examples ## 🤝 Want to Contribute? ## 🏁 Final Thoughts RunAPI just got a solid upgrade. The latest version introduces schema support, improves internal architecture, and sets the foundation for better testing and database extensibility — while keeping RunAPI lightweight and developer-friendly. If you’re building APIs with Python and like file-based routing + FastAPI under the hood, this release is for you. RunAPI now supports schemas, making it easier to: This brings RunAPI closer to real-world production needs while still keeping things simple. A number of internal improvements were merged to clean things up: These changes don’t affect public APIs but make RunAPI more robust and future-proof. RunAPI currently supports two storage backends: If SQLAlchemy isn’t present, RunAPI gracefully falls back to in-memory storage — no crashes, no surprises. With schema support in place, the next focus areas are: Although InMemory and SQLAlchemy backends already exist, we want: RunAPI is still evolving and contributions are very welcome. 👉 GitHub repo: https://github.com/Amanbig/runapi 👉 Issues: https://github.com/Amanbig/runapi/issues This release is less about flashy features and more about laying a solid foundation. Schemas unlock safer APIs. Cleaner internals unlock faster development. And the roadmap keeps RunAPI flexible without bloating it. If you try it out, feedback is more than welcome 🙌 Templates let you quickly answer FAQs or store snippets for re-use. Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse - Define request and response models - Validate inputs consistently - Keep APIs structured as they grow - Python 3.12 compatibility fixes (datetime.utcnow() → datetime.now(timezone.utc)) - Safer handling of non-Pydantic models - Removed deprecated Pydantic v1 patterns - Better module loading safety checks - Cleaner route name generation - InMemory storage (default, zero dependencies) - SQLAlchemy storage (used only if SQLAlchemy is installed) - lightweight by default - flexible for more serious use cases - More tests around schemas - Edge-case tests for routing and auth - Stronger confidence as features grow - a clear shared interface - cleaner backend selection - easier future extensions (Redis, etc.) - Schema usage guides - Storage behavior explained clearly - Real-world CRUD examples - Storage abstraction 🗄️ - Examples & templates 🧱