-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(core): Add addEventProcessor
method
#9554
Conversation
size-limit report 📦
|
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.
We need migration docs in MIGRATION.md
Good point! Small note, with the upcoming hub & scope changes this also means that we'll update this to put the event processors on the isolation scope instead of the client, but that doesn't affect this PR (as it is a future change, that we can do under the hood in v8) |
f8ed063
to
5b64856
Compare
And deprecate `addGlobalEventProcessor()` and `getGlobalEventProcessors()`. In v8, all event processors will be on the client only, streamlining this a bit and preventing global "pollution".
5b64856
to
4dc2e3e
Compare
And deprecate
addGlobalEventProcessor()
andgetGlobalEventProcessors()
.In v8, all event processors will be on the client only, streamlining this a bit and preventing global "pollution".
Closes #9082