-
Notifications
You must be signed in to change notification settings - Fork 42
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
setUserInfo should not overwrite previous usage #254
Comments
Hi @brunovsiqueira, This is expected behavior as That said, I agree we should have a separate method to add or change additional properties for the current user without modifying the user info already provided. I'll look into adding it. |
Hi @fuzzybinary. Thanks for your attention. Ok, it's clear now and makes sense. I have implemented what you suggested and it works properly. I agree with you that would be helpful having a separate method to add or change extra properties. If you want, you can close this issue or mark it with feature request. |
This allows users to set additionally attributes on a user without having to reset their name, id or email. Fixes #254
This allows users to set additionally attributes on a user without having to reset their name, id or email. Fixes #254
|
Hi there. I'd like to discuss if this is the expected behavior.
Describe what happened
When you use "setUserInfo" method in order to set User RUM information more than once, only what you have set in the latest usage appear in RUM logs. It seems to clear all user information you have set even if you are setting only additional info.
Steps to reproduce the issue:
Call "setUserInfo" with only id, name and email.
Afterward, call "setUserinfo" with only "extraInfo" map.
In RUM log, you only see the extraInfo propertities you have set.
Describe what you expected:
In my opinion, it should compose userInfo instead of overwriting it. In RUM logs, I should see all the basic user info (id, name and email) added by the extraInfo I have set separeteley.
Additional context
The text was updated successfully, but these errors were encountered: