Added new logs and improved coverage for Wallets operations #43
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.
This pull request adds comprehensive wallet logging to match the web SDK, updates the structure for logs sent to DataDog, and replaces
OSLogTypewith a customLogLeveltypeNew Logging Coverage
Added new log event constants and implemented logging across:
All logs follow a three-phase pattern from the web SDK, (
start→success/error) with contextual metadata (transaction IDs, addresses, chain types, error messages)Structured Logging
Updated
DataDogLoggerProviderandOSLoggerProviderto format messages with key=value pairs:DataDog now receives formatted message strings only (with base service/platform attributes), which will be formatted into proper metadata on DataDog through a grok parser we'll implement for the mobile SDK
Custom LogLevel Enum
Replaced
OSLogTypewith a customLogLevelenum containing only the four levels fromLoggerProvider:The default level changed from
.defaultto.error