-
Notifications
You must be signed in to change notification settings - Fork 53
[No Jira][v3] Adapt internal-testing-tools-package to v3 #1065
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
Merged
sbarrio
merged 4 commits into
feature/v3
from
sbarrio/v3/adapt-internal-testing-tools-package-to-v3
Dec 9, 2025
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,7 +14,7 @@ import DatadogInternal | |
| public class DdInternalTestingImplementation: NSObject { | ||
| @objc | ||
| public func clearData(resolve:RCTPromiseResolveBlock, reject:RCTPromiseRejectBlock) -> Void { | ||
| let coreProxy = (DatadogSDKWrapper.shared.getCoreInstance() as! DatadogCoreProxy) | ||
| let coreProxy = CoreRegistry.default as! DatadogCoreProxy | ||
| coreProxy.waitAndDeleteEvents(ofFeature: "rum") | ||
| coreProxy.waitAndDeleteEvents(ofFeature: "logging") | ||
| coreProxy.waitAndDeleteEvents(ofFeature: "tracing") | ||
|
|
@@ -26,7 +26,7 @@ public class DdInternalTestingImplementation: NSObject { | |
| @objc | ||
| public func getAllEvents(feature: String, resolve:RCTPromiseResolveBlock, reject:RCTPromiseRejectBlock) -> Void { | ||
| do { | ||
| let coreProxy = (DatadogSDKWrapper.shared.getCoreInstance() as! DatadogCoreProxy) | ||
| let coreProxy = CoreRegistry.default as! DatadogCoreProxy | ||
| let events = coreProxy.waitAndReturnEventsData(ofFeature: feature) | ||
| let data = try JSONSerialization.data(withJSONObject: events, options: .prettyPrinted) | ||
| resolve(String(data: data, encoding: String.Encoding.utf8) ?? "") | ||
|
|
@@ -39,9 +39,10 @@ public class DdInternalTestingImplementation: NSObject { | |
|
|
||
| @objc | ||
| public func enable(resolve:RCTPromiseResolveBlock, reject:RCTPromiseRejectBlock) -> Void { | ||
| DatadogSDKWrapper.shared.addOnCoreInitializedListener(listener: {core in | ||
| DatadogSDKWrapper.shared.addOnSdkInitializedListener(listener: {core in | ||
| let proxiedCore = DatadogCoreProxy(core: core) | ||
| DatadogSDKWrapper.shared.setCoreInstance(core: proxiedCore) | ||
| CoreRegistry.unregisterDefault() | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Calling register directly with the same name does not overwrite its value, so we need to call |
||
| CoreRegistry.register(default: proxiedCore) | ||
| }) | ||
| resolve(nil) | ||
| } | ||
|
|
@@ -51,9 +52,10 @@ public class DdInternalTestingImplementation: NSObject { | |
| public class DdInternalTestingNativeInitialization: NSObject { | ||
| @objc | ||
| public func enableFromNative() -> Void { | ||
| DatadogSDKWrapper.shared.addOnCoreInitializedListener(listener: {core in | ||
| DatadogSDKWrapper.shared.addOnSdkInitializedListener(listener: {core in | ||
| let proxiedCore = DatadogCoreProxy(core: core) | ||
| DatadogSDKWrapper.shared.setCoreInstance(core: proxiedCore) | ||
| CoreRegistry.unregisterDefault() | ||
| CoreRegistry.register(default: proxiedCore) | ||
| }) | ||
| } | ||
| } | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I removed these for two reasons:
And for those curious, this worked fine on v2 because the DatadogSdkWrapper kept a local reference to the core sdk instance, and the internal testing tools were wrapping that one instead, so calls to Datadog.isInitialized would still work fine as they would not deal with the wrapped core but with the internal SDK one.