Remove ContentPainterElement Class Reflection from Telemetry#2714
Merged
Conversation
ambushwork
marked this pull request as ready for review
June 10, 2025 08:38
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #2714 +/- ##
===========================================
+ Coverage 69.84% 69.85% +0.01%
===========================================
Files 823 823
Lines 30624 30626 +2
Branches 5157 5157
===========================================
+ Hits 21389 21393 +4
- Misses 7784 7789 +5
+ Partials 1451 1444 -7
🚀 New features to boost your workflow:
|
0xnm
approved these changes
Jun 10, 2025
aleksandr-gringauz
approved these changes
Jun 11, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do?
ContentPainterElementclass reflection contributes a high volume to our telemetry log while we don't have any action on that, because it becomes a normal case if the client is usingcoil3instead ofcoil2, so removing it from TelemetryReview checklist (to be filled by reviewers)