Update statement about default view tracking strategy in the docs#1003
Merged
0xnm merged 1 commit intoAug 22, 2022
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1003 +/- ##
==========================================
- Coverage 83.13% 83.07% -0.06%
==========================================
Files 267 267
Lines 9079 9079
Branches 1461 1461
==========================================
- Hits 7547 7542 -5
- Misses 1131 1132 +1
- Partials 401 405 +4
|
jtappa
approved these changes
Jul 28, 2022
xgouchet
approved these changes
Aug 1, 2022
0xnm
deleted the
nogorodnikov/update-docs-about-rum-default-view-tracking
branch
August 22, 2022 07:14
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?
#521 added sensible defaults to the RUM config, but docs were not updated. This PR fixes that.
Note: This PR is targeting
masterbranch, because it is related to the functionality which was released a long time ago already. Once merged, it needs to be moved todevelopas well.Review checklist (to be filled by reviewers)