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-449: Enable RUM and Traces for Logs #601

Closed

Conversation

jonathanmos
Copy link
Member

What does this PR do?

A brief description of the change being made with this pull request.

Motivation

What inspired you to submit this pull request?

Additional Notes

Anything else we should know when reviewing?

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
  • If this PR is auto-generated, please make sure also to manually update the code related to the change

@jonathanmos jonathanmos force-pushed the jmoskovich/rum-449/leverage-rum-and-traces branch 3 times, most recently from d87a4ab to 7808272 Compare February 1, 2024 14:45
@jonathanmos jonathanmos force-pushed the jmoskovich/rum-449/leverage-rum-and-traces branch 2 times, most recently from c598c0b to d8749e0 Compare February 4, 2024 10:55
@jonathanmos jonathanmos force-pushed the jmoskovich/rum-449/leverage-rum-and-traces branch from d8749e0 to 2d114a1 Compare February 4, 2024 11:18
@jonathanmos jonathanmos marked this pull request as ready for review February 4, 2024 11:41
@jonathanmos jonathanmos requested a review from a team as a code owner February 4, 2024 11:41
@jonathanmos jonathanmos requested a review from 0xnm February 15, 2024 08:29
Copy link
Member

@0xnm 0xnm left a comment

Choose a reason for hiding this comment

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

I left some comments about the naming.

Copy link
Contributor

@louiszawadzki louiszawadzki left a comment

Choose a reason for hiding this comment

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

The Android part looks good to me.
Let's wait for the iOS part to be done before merging.

One small improvement we could have made: here there is no reason to pass the config fields in the additionalConfig object. By doing so we lose a tiny bit of type safety, but it's not a huge deal.
Although I think that if they're not needed we should remove the fields from the DdSdkConfiguration since we are not reading them from here as it can be misleading.
Ultimately we should get rid of this additionalConfig field in a separate PR.

Comment on lines +140 to +141
configuration.bundleLogsWithRum,
configuration.bundleLogsWithTraces
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we also need to pass the data here since we seem to get it from the additionalConfig field anyway?

@louiszawadzki
Copy link
Contributor

I'm closing this PR for clarity, since the work is going to continue on #624

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