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
I have many scenarios where I would like to only turn on a few loggers based and setup custom filtering based on some configuration.
For example, I may just want to filter by API calls and Keyboard shortcuts. The LogLevel system isn't fine grained enough to support this. Right now the filter is handled here in the Logger:
boolisLoggable(Level value) => (value >= level);
One proposal would be to introduce an interface called LogFilter. It would look like:
I have many scenarios where I would like to only turn on a few loggers based and setup custom filtering based on some configuration.
For example, I may just want to filter by
API calls
andKeyboard shortcuts
. The LogLevel system isn't fine grained enough to support this. Right now the filter is handled here in the Logger:One proposal would be to introduce an interface called
LogFilter
. It would look like:Then, we could update the signature to:
Just a rough idea. Any impact this would have on the current logging implementation?
The text was updated successfully, but these errors were encountered: