feat: new endpoint /v1/autotranslate.getProviderUiMetadata - #42150
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: ae345cf The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
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 selected for processing (6)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (6)
🧰 Additional context used🧠 Learnings (2)📚 Learning: 2026-02-26T19:25:44.063ZApplied to files:
📚 Learning: 2026-02-26T19:25:44.063ZApplied to files:
🪛 LanguageTool.changeset/ddp-migrate-get-provider-ui-metadata.md[style] ~5-~5: To elevate your writing, try using more formal phrasing here. (CONTINUE_TO_VB) WalkthroughThe change adds an authenticated REST endpoint for auto-translate provider metadata. The client uses this endpoint for provider loading. The existing real-time method now logs deprecation information and remains available until version 9.0.0. ChangesAuto-translate provider metadata
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature Sequence Diagram(s)sequenceDiagram
participant AutoTranslateClient
participant AutoTranslateAPI
participant TranslationProviderRegistry
AutoTranslateClient->>AutoTranslateAPI: GET /v1/autotranslate.getProviderUiMetadata
AutoTranslateAPI->>TranslationProviderRegistry: Read provider metadata
TranslationProviderRegistry-->>AutoTranslateAPI: Provider metadata
AutoTranslateAPI-->>AutoTranslateClient: Return providers
Suggested labels: Suggested reviewers: Merge Risk: ⚪ Minimal · up to The REST migration uses the matching providers response shape, and the legacy method retains its established deprecation behavior. No actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Warning Errors were encountered while retrieving linked issues. Errors (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
All reported issues were addressed across 6 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #42150 +/- ##
===========================================
+ Coverage 69.44% 69.46% +0.02%
===========================================
Files 4323 4323
Lines 180471 180477 +6
Branches 31709 31735 +26
===========================================
+ Hits 125320 125361 +41
+ Misses 50097 50065 -32
+ Partials 5054 5051 -3
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
hey can you pleasee tell me why i cannot add the labels to my PRs |
Proposed changes (including videos or screenshots)
Issue(s)
ARCH-2307
Steps to test or reproduce
Further comments
Summary by CodeRabbit
New Features
Deprecations