-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DEBUG-3568 Remove transport API instance/spec branching #4480
Conversation
Thank you for updating Change log entry section 👏 Visited at: 2025-03-17 13:26:38 UTC |
Datadog ReportBranch report: ✅ 0 Failed, 20614 Passed, 1458 Skipped, 3m 8.47s Total Time |
e028f90
to
5c5916c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4480 +/- ##
==========================================
- Coverage 97.76% 97.76% -0.01%
==========================================
Files 1390 1390
Lines 84748 84741 -7
Branches 4281 4281
==========================================
- Hits 82856 82843 -13
- Misses 1892 1898 +6 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5c5916c
to
71618a4
Compare
71618a4
to
8cab7e1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏🏼 awesome
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
What does this PR do?
This PR moves toward having transport API Instance and Spec classes being API-specific. Currently, these classes are one for a component (e.g. remote/tracing/DI) but these classes combine functionality from multiple APIs and then downstream code has API-specific classes again that reference these "combined" Instance and Spec classes.
The idea is to have all of the transport-related classes be scoped to one API.
This PR removes the branching of one API -> multiple APIs -> one API again but leaves tracing instance & spec classes unchanged which makes them defined in a slightly different way from remote & DI counterparts.
Motivation:
Making transport code more readable.
Change log entry
None
Additional Notes:
How to test the change?
Existing unit tests