-
Notifications
You must be signed in to change notification settings - Fork 176
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
Replace account id on rudderstack with hash id #3089
Conversation
Your Render PR Server URL is https://near-wallet-pr-3089.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-cj43kup8g3n78m4sd2rg. |
✅ Deploy Preview for unrivaled-zabaione-2fe19c ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for glittering-pavlova-0e9247 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Looking good overall, but I remain strongly in favor of computing the hash every time. We don't get any noticeable benefit from caching, we only introduce the possibility of reporting the wrong data.
@@ -88,3 +93,16 @@ export const resetUserState = () => { | |||
} | |||
return rudderanalytics.reset(); | |||
}; | |||
|
|||
export function accountIdToHash(accountId) { | |||
if (!accountIdHash) { |
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.
Introducing state here now has introduced the potential for an event to be reported under the wrong accountId. Can we please compute the hash every time so as not to add any further complexity to event reporting?
This PR contains implementation to replace existing
account id
details on RudderStack metrics with hash id.The team decided to not track account Id from RudderStack on Transfer Wizard. So similar to how it is implemented on
near-discovery
we hash the accountId and use it instead.This change need to be published to prod as soon as it passes the review.