spectree VS fastapi

For those of you that are fans of Pydantic: https://github.com/0b01001001/spectree (this is cross-platform with flask, falcon, and starlette :) It also doesn't re-implement anything the encode/starlette developers have already implemented, or have in the works for no specific reason. I'm not a huge fan of this design pattern, I'm more a lean/mean sort of fellow. openapi schema generation exists in starlette ... and you likely already are doing some sort of type validation once in your forms, json, orm, sql layer, or all four. An additional layer to validate "automatically" in your response (lol no), or in your request ... aren't all that useful imo.

only having 1 maintainer

From the official docs:

To save time here, I have prepared a basic Python application developed on FastAPI and if you want to follow along you can get the code from GitHub Repository here.

This repository contains code for asynchronous example api using the Fast Api framework ,Uvicorn server and Postgres Database to perform crud operations on notes.

That sounds like the perfect job for our open-source lib NiceGUI. It is an UI framework on top of FastAPI. That means you can easily setup HTTPS POST endpoints to save the incoming data to a file or database. With very little effort you can also create your webpage which reads the data and displays it.

This package extends the FastAPI response model schema allowing you to have a common response wrapper via a fastapi.routing.APIRoute.

fully type-annotated options for building an API are available - one popular option is FastAPI and everything you expose is declared through pydantic. There is nothing as productive in Go I'm afraid.