mirror of
https://github.com/OpenBB-finance/OpenBB.git
synced 2026-10-27 20:42:26 +00:00
915bfa48f1
* feat: Add Flask-to-OpenBB enterprise migration toolkit - Implement Router.from_flask() for zero-touch legacy API conversion - Enable 4-hour migration vs 6-month traditional rewrite (80% cost reduction) - Generate FastAPI endpoints from Flask routes with automatic type validation - Support enterprise consulting services and custom integration workflows Demonstrates OpenBB's competitive advantage for institutional client migrations. Complements existing Workspace applications like Open Portfolio suite. * chore: Resolve .gitignore conflict and add common ignores * refactor: implement Phase 1 Flask integration architecture- Move Flask conversion logic to openbb_core.app.utils.flask- Add Flask detection to extension_loader - Integrate with OpenBB's core extension system- Add Flask dependency validation with sys.modules checkingAddresses @deeleeramone's architectural feedback for native OpenBB integration. * docs: add Flask direct entry point demos- demo_direct_flask_entry_point.py: shows direct Flask instance reference- example_pyproject_flask_entry.toml: demonstrates pyproject.toml configurationSupports new architecture eliminating wrapper extensions. * Implement Phase 1 Flask adapter per code review feedback - Minimal working implementation with Flask detection and router creation - Removes complex code generation logic for focused Phase 1 delivery - Establishes foundation for Phase 2 route conversion features * Fix Flask integration: Replace missing FlaskToOpenBBAdapter with WSGIMiddleware - Remove FlaskToOpenBBAdapter which was not implemented - Use FastAPI's WSGIMiddleware to mount Flask apps directly - Update extension_loader to use returned Router object - Convert utils.py to utils/__init__.py to support flask submodule - Addresses PR review comment about unhandled AttributeError * Address PR review feedback: fix Flask imports and remove unused files - Revert .gitignore to upstream/develop - Remove AI-generated demo/example files and flask_adapter extension - Move Flask/werkzeug imports inside conditional blocks to avoid ImportError - Use lazy imports via __getattr__ in utils/flask/__init__.py - Add Flask tests with @pytest.mark.skipif markers * Force APIRouter.include_router to propagate Mount paths instead of dropping them. (#1) This change ensures that mounted ASGI applications (such as Flask apps wrapped in WSGIMiddleware) are not dropped when `APIRouter.include_router` is called. Previously, while the initial load in `ExtensionLoader` worked as expected, the `Mount` objects were ignored by FastAPI's default inclusion logic. This caused the mounted elements to be lost during the final application assembly, resulting in 404 errors for the Flask routes. This fix overrides the inclusion logic to manually propagate `Mount` objects downstream. * feat(flask): Add metadata layer for OpenAPI documentation Enhance Flask-to-OpenBB converter with structured docstring parsing: - Parse Google-style docstrings (summary, description, params) - Extract parameter descriptions from Args section - Pass metadata to Router.command() for rich OpenAPI docs This addresses PR feedback to provide tangible benefit by generating comprehensive API documentation for migrated Flask routes. * feat(flask): Implement manual OpenAPI spec generation and attachment - Add FlaskParam and FlaskRouteInfo TypedDict for type-safe metadata - Implement OpenAPISpecGenerator for Flask→OpenAPI conversion - Extract route metadata via FlaskIntrospector - Attach generated spec to router.openbb_openapi_spec_ext - Add unit tests (3/3 passing) Addresses WSGI/mount boundary issue where Router.command metadata cannot propagate through WSGIMiddleware. Spec attached to router instance for downstream OpenAPI assembly. Resolves maintainer feedback on PR #7264 * feat(flask): Implement FlaskMountRegistry for multiple mount support - Add FlaskMountRegistry class for centralized OpenAPI spec management - Replace router.openbb_openapi_spec_ext with registry pattern - Support multiple Flask apps at different mount prefixes - Automatic path rewriting in aggregated OpenAPI specs - Add registry test case (4/4 tests passing) Addresses @deeleeramone's feedback on PR #7264 regarding router attribute fragility and multiple mount support. Registry provides lifecycle-independent state management and enables enterprise scenarios with multiple Flask apps. Resolves: OpenBB-finance/OpenBB#7264 (partial) * feat(core): load Flask apps as openbb_core_extension WSGI sub-apps A Flask app referenced directly by an openbb_core_extension entry point is mounted via WSGIMiddleware and its routes are introspected into openapi.json (operationId/widgetId/mcp_tool, parameters, request bodies, security, widget_config and HTML widgets) so the widget factory and MCP server can discover them. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * test(core): 100% coverage for flask utils + flask dev dependency Add branch-coverage tests for the Flask integration package (introspection, AST analysis, docstrings, OpenAPI generation, registry, loader, detection) and declare flask as a dev dependency so the suite runs in CI. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(flask): treat f-string returns as HTML responses * fix(flask): mount via a2wsgi instead of deprecated starlette WSGIMiddleware - add openbb-core[flask] extra (flask, a2wsgi); a2wsgi resolved through require_optional - run the WSGI serve test through mount_flask_extensions; drop httpx importorskip - core CI installs [pandas,flask] and httpx2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * test(flask): cover failed entry point loads; narrow optional types for ty Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Danglewood <85772166+deeleeramone@users.noreply.github.com> Co-authored-by: deeleeramone <> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>