Feat: Set user context #23
Conversation
Changes primarily reflect setting user context early in App.tsx. Additionally this context is added to outgoing GET and POST requests from scope to transfer user context to connected services.
| placeholder={item.placeholder} | ||
| onPressIn={() => { | ||
| dispatch({ type: 'FILL_FIELDS', payload: 'dummydata' })} | ||
| dispatch({ type: 'FILL_FIELDS', payload: 'dummydata', onScope:email ? email:null})} |
There was a problem hiding this comment.
@dgbailey this onScope stuff works great. Wondering, is this a property or part of the redux or React Context API? Or is it more like a property you're declaring and it simply gets passed through.
There was a problem hiding this comment.
Hey @thinkocapo just declaring it myself so it gets passed.
| setProductData(null); | ||
| let se, customerType, email; | ||
| Sentry.withScope(function(scope) { | ||
| [ se, customerType ] = [scope._tags.se, scope._tags.customerType ] |
There was a problem hiding this comment.
@dgbailey what was the workaround for letting you take _tags data off of the scope? Wasn't it preventing you at first?
There was a problem hiding this comment.
@thinkocapo Turns out the compiler will warn about what is deemed inappropriate use of a protected field but do nothing to prevent it at runtime.
|
@dgbailey I saw all the backend transactions + errors (Flask) had the user email set as well. We have a different todo open for some user info missing on Springboot or Express transactions, but someone is already on it. That's a backend problem. Now the frontend looks solid. 👍 merge it |
2 participants
Changes primarily reflect setting user context early in App.tsx. Additionally this context is added to outgoing GET and POST requests from scope to transfer user context to connected services.
Example Transactions:
https://sentry.io/organizations/testorg-az/discover/results/?field=transaction&field=user.email&field=count%28%29&name=Transactions+by+Volume&query=project%3Areact-native+has%3Auser.email+event.type%3Atransaction&sort=-count&statsPeriod=7d&yAxis=count%28%29