Skip to content
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

RUM-917 Improve telemetry of type mismatch #1863

Merged
merged 2 commits into from
Jun 6, 2024

Conversation

maciejburda
Copy link
Member

What and why?

Adds extra telemetry info to to help resolving type mismatch error in Session Replay.

How?

Expands error type to contain from and to types of the wireframe that conflicted.

Review checklist

  • Feature or bugfix MUST have appropriate tests (unit, integration)
  • Make sure each commit and the PR mention the Issue number or JIRA reference
  • Add CHANGELOG entry for user facing changes

Custom CI job configuration (optional)

  • Run unit tests for Core, RUM, Trace, Logs, CR and WVT
  • Run unit tests for Session Replay
  • Run integration tests
  • Run smoke tests
  • Run tests for tools/

@maciejburda maciejburda marked this pull request as ready for review May 27, 2024 15:37
@maciejburda maciejburda requested review from a team as code owners May 27, 2024 15:37
@maciejburda maciejburda force-pushed the maciey/RUM-917/wireframe-type-mismatch branch from 5f3af49 to d6ff2b3 Compare June 4, 2024 11:29
@datadog-datadog-prod-us1
Copy link

Datadog Report

Branch report: maciey/RUM-917/wireframe-type-mismatch
Commit report: 62968f3
Test service: dd-sdk-ios

✅ 0 Failed, 253 Passed, 0 Skipped, 13.51s Total Time

}

// MARK: - Resolving Mutations

internal typealias WireframeMutation = SRIncrementalSnapshotRecord.Data.MutationData.Updates

internal enum WireframeMutationError: Error {
internal enum WireframeMutationError: Error, Equatable {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this enum is automatically conforming to Equatable since the associated values you added are String. I don't think it's an issue to add it explicitly, but I was wondering if I missed anything here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assertions in test were complaining about it. I think that once enum has associated values it needs to be explicitly specified

@maciejburda maciejburda merged commit 46c6816 into develop Jun 6, 2024
4 checks passed
@maciejburda maciejburda deleted the maciey/RUM-917/wireframe-type-mismatch branch June 6, 2024 14:10
This was referenced Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants