How poseidon1998/brainsmith_backend works
Project type and purpose
• From the folder names and files, this looks like a standalone Python‑based backend service exposing a set of HTTP API endpoints (likely using FastAPI or a similar framework).
• Its purpose is to process “patch” operations on some polygon graph data, manage database interactions, use a nomenclature config, and export or save metadata.
File structure
• Top‑level files:
• requirements.txt — lists Python dependencies for the API and libraries.
• save_metadata.py — a standalone script to extract or persist metadata.
• The “app/api” package:
• main.py — entry point for the web server, routing, and application startup.
• functions.py — core business logic for each endpoint.
• models.py — request/response data models (e.g., Pydantic schemas).
• dependencies.py — dependency injection definitions (e.g., DB session, config loader).
• The “lib” package:
• patch.py — logic for creating or applying a patch to polygon data.
• patch_db.py — database CRUD operations related to patches.
• polygon_graph.py — graph data structures and algorithms on polygon meshes.
• path_config.py + nomenclature.json — configuration loader and static naming conventions.
README for additional insights
• The README is empty, so we rely on file names and typical conventions.