Skip to content

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

Closed
fgm opened this issue Dec 12, 2016 · 1 comment
Closed

Support per-sender processors #24

fgm opened this issue Dec 12, 2016 · 1 comment

Comments

@fgm
Copy link
Owner

fgm commented Dec 12, 2016

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 the ConsoleSender 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 the Logger level.

@fgm
Copy link
Owner Author

fgm commented Dec 16, 2016

This is now happening as a side-effect of #23.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant