-
Notifications
You must be signed in to change notification settings - Fork 6
Support per-sender processors #24
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
Labels
Comments
This is now happening as a side-effect of #23. |
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Feb 28, 2019
fgm
added a commit
that referenced
this issue
Mar 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, all senders receive the same messages, extended by the same processors.
However, there are cases where some senders would be better off without some processors, or possibly with alternate ones. A typical case in point would be the
BrowserProcessor
on theConsoleSender
in the browser: this is almost always useless, and adds unwanted noise to the console output.It would be nice to have a way to configure processors at the
Sender
level too, not just at theLogger
level.The text was updated successfully, but these errors were encountered: