feat: add Pydantic Logfire OFREP API - #1484
jonathannorris wants to merge 1 commit into
Conversation
Signed-off-by: Jonathan Norris <jonathan.norris@dynatrace.com>
✅ Deploy Preview for openfeature ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe change adds a Pydantic Logfire OFREP API descriptor and registers it in the exported ecosystem API list. ChangesOFREP API registration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to The OFREP API entry is registered without any supported merge-blocking issue. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
Comment |
Summary
pydantic-logfire-no-fill.svglogo.Notes
Pydantic doesn't publish its own OpenFeature provider for any language; their docs point users at the community OFREP providers (
@openfeature/ofrep-web-provider,@openfeature/ofrep-provider,openfeature-provider-ofrep, and the Kotlin/Swift*-sdk-contribOFREP providers). So this PR only adds the OFREP API entry.Question for reviewers: should we also add provider-level entries for vendors like this that are OFREP-only? Today they show up solely under OFREP APIs, which means someone browsing the ecosystem by language won't find Pydantic at all even though every OFREP-supported language works against it.