[No Jira][V3] Refactor RumConfiguration properties #1087
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?
This PR modifies the configuration object types so the following properties are now moved into the rumConfiguration object:
It also exposes optional configuration objects for Rum, Logs and Trace on DatadogProviderConfiguration, allowing for easier configuration without the need to set and create separate configuration objects and having to set each property one by one.
Motivation
We need to make sure that domain related properties are properly placed under the right configuration for their target module. We also need to make configuration as easy as possible while retaining flexibility.
Review checklist (to be filled by reviewers)