-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[RUM] React Native - Update setUser method to setUserInfo #28949
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] React Native - Update setUser method to setUserInfo #28949
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well done 🙌
content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/advanced_configuration.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again 🙇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do? What is the motivation?
This update reflects a change introduced in version 2.6.5 of the React Native SDK. The method previously used for setting user information—
setUser
—has been renamed tosetUserInfo
. This PR updates the documentation accordingly to ensure consistency with the current SDK API.PR introducing the change
Merge instructions
setUserInfo
is the recommended way to clear user data upon logout.Note: It was clarified that the correct way to clear the user object it's by using
setUser
by @sbarrio on the review comment.Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes