fix: address gaps#19
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests.
|
|
|
Claude encountered an error —— View job Code Review Complete ✅SummaryThis PR successfully addresses three gaps identified during Bridge component replacement:
Verdict: Approve with minor suggestions - All changes are well-implemented, fully tested (100% coverage), and backwards compatible. Quality Gate passed. Two minor suggestions below for consideration. Detailed Review✅ Strengths
💡 Suggestions (Optional)1. Documentation Enhancement (Minor)File: The AGENTS.md update mentions **api.core** | Versioned API router and FastAPI factory | ... `init_api(root_path, lifespan, exception_handler_registrations, versions=None, version_exception_handler_registrations=None, **fastapi_kwargs)` — creates a `FastAPI` with standard Foundry exception handlers; when *versions* is supplied, automatically calls `get_versioned_api_instances()`, applies optional per-version exception handlers, and mounts each sub-app at `/{version}` on the root appThis makes the new capability more discoverable. 2. SonarQube Issues (Quality Gate Passed, but 2 new issues)The SonarQube report shows 2 new issues (Quality Gate still passed). These are likely minor code smells. Without access to the detailed SonarQube report, I cannot identify the specific issues, but common S1192 violations in test files include:
Recommendation: Review the SonarQube analysis to identify and address these 2 issues before merge. 🔍 Detailed File Review
|

This PR addresses a few gaps identified while trying to replace the corresponding components in Bridge:
FoundryContext.python_versionto replaceplatform.python_version()calls throughout the codeinit_api()so callers don't need to doget_versioned_api_instancesthemselvesFoundryContext.env_prefixin Sentry, log and auth settings