[RUM-11289][FO]: supporting user debug logs#2819
Conversation
| reportTelemetry { FO_TELEMETRY_FAILED_MESSAGE } | ||
| } | ||
|
|
||
| private fun logToUser(messageProvider: () -> String) { |
There was a problem hiding this comment.
very minor nit:
| private fun logToUser(messageProvider: () -> String) { | |
| private fun logDebugToUser(messageProvider: () -> String) { |
There was a problem hiding this comment.
Bit refactored to use for whole class. The method accepts log level now
| eventTime = getEventTime(attributes) | ||
| ) | ||
| ) | ||
| logToUser { "Feature Operation `$name` (operationKey `$operationKey`) was started." } |
There was a problem hiding this comment.
I'm not the native speaker, but I would suggest to remove was here and below. Like operation started, operation successfully ended.
It is quite common to use such simpler form in log messages.
pinging @fuzzybinary / @awforsythe for the input
There was a problem hiding this comment.
I agree, I can update on the iOS side
e7803bf to
49f23a5
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/featureoperations #2819 +/- ##
=============================================================
+ Coverage 69.99% 70.11% +0.12%
=============================================================
Files 835 835
Lines 31412 31418 +6
Branches 5272 5272
=============================================================
+ Hits 21985 22027 +42
+ Misses 7928 7916 -12
+ Partials 1499 1475 -24
🚀 New features to boost your workflow:
|
What does this PR do?
Supports debug logs for FO methods.
Motivation
Logs aimed to help customers check the correctness of integration.
Review checklist (to be filled by reviewers)