I am designing an app that has a database, a CRUD web interface to manage its content, and exposing a REST API to be called by an external UI written in React. I am using native Flask Blueprints, SQLAlchemy, along with Marshmallow for API serialization.
The way I have structured Blueprints, based on what I learned from the Flask docs, seems unnecessarily complicated:
app.py->__init__.py.create_app()registers blueprints- "factory" Flask pattern
- each blueprint imports from a
routesmodule register_blueprintspecifies two blueprints one for HTML, another for API as each has a differenturl_prefix
- each
routesmodule__init__.py- imports Blueprint, then
- creates the blueprint instances for html and api, then
- imports the actual routes for the module (e.g.
from routes.user import routes)
- each
routesimplementation- imports the blueprints created in the module
- imports the SQLAlchemy model and Marshmallow schema
- creates the code for the routes, and decorates with the correct blueprint depending on HTML or API
- each model imports required elements for SQLAlchemy
So the SQLAlchemy approach seems just right: in one place I define all the characteristics of the model and thus the associated database tables, as well as the schema for JSON output of my API.
But the Blueprints approach seems convoluted, with dependencies scattered about -- to define one new route, I typically have to modify three files:
appmodule (__init.py__)routesmodule for the specific route (routes/user/__init.py__)routesimplementation for the specific route (routes/user/routes.py)- and each of these implicitly depend on the model for the entity (e.g.
user)
All of this is functional, but I am assuming there's a simpler way to approach the problem that I have not yet fully grasped. Is there a simpler, cleaner way to implement this?
source https://stackoverflow.com/questions/77664284/flask-blueprints-with-sqlalchemy-for-apis-what-can-i-do-to-simplify
Comments
Post a Comment