Add .NET support to Unleash provider and fix hrefs#1399
Conversation
…hrefs Signed-off-by: André Silva <2493377+askpt@users.noreply.github.com>
Signed-off-by: André Silva <2493377+askpt@users.noreply.github.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: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThree dataset files are updated for .NET SDK references: the OpenTelemetry hook href is corrected to point to the dotnet-sdk repository, the Flagd provider .NET href is updated from Changes.NET SDK Metadata Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Comment |
Update the Unleash provider to include .NET technology and correct hrefs for both the Unleash and OpenTelemetry hooks. This enhancement adds support for .NET in the Unleash provider while ensuring accurate links for existing technologies.