You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(core): Run client eventProcessors before global ones (#9032)
I noticed that while from an API POV the current behavior makes kind-of
sense IMHO:
1. Run global event processors
2. Run scope event processors
3. Run client event processors
It is potentially breaking, as if we rewrite integrations to use the new
client processors, their processing will run after any user global event
processors, leading to potentially unexpected outcomes.
So this PR changes this to instead run them in this order:
1. Run client event processors
2. Run global event processors
3. Run scope event processors
Which should be more stable for now.
In v8, we should update this to run a more sensible order:
1. Global
2. Client
3. Scope
0 commit comments