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
Merge #220: Add log levels and advertise them to users via logging callback
515ce93 Logging: Pass LogData struct to logging callback (Cory Fields)
213574c Logging: reclassify remaining log messages (Cory Fields)
e4de041 Logging: Break out expensive log messages and classify them as Trace (Cory Fields)
408874a Logging: Use new logging macros (Cory Fields)
67b092d Logging: Disable logging if messsage level is less than the requested level (Cory Fields)
d0a1ba7 Logging: add log levels to mirror Core's (Cory Fields)
463a829 Logging: Disable moving or copying Logger (Cory Fields)
83a2e10 Logging: Add an EventLoop constructor to allow for user-specified log options (Cory Fields)
Pull request description:
Fixes#215. Alternative to #216.
This is is implemented roughly as suggested [here](#216 (comment)):
- Adds log levels.
- Adds an additional "Raise" log level.
- Uses the 'Trace' level by default, so existing behavior is unchanged.
- Remains backwards-compatible via a new (deprecated) EventLoop constructor.
Users should not observe any behavioral difference. However, they can now change the log level (using the `EventLoop` constructor which takes a `LogOptions`) to set a lower level.
Once merged, Core should take advantage of the new functionality:
- Update the callback function signature.
- Set the requested log level.
- Map mp log levels to Core ones inside the callback.
ACKs for top commit:
ryanofsky:
Code review ACK 515ce93. Just rebased and fixed compile error caused by new log print since last review
Tree-SHA512: 835f83f714d9bcff92ad480b53e65b929812e521c750a80dea0c42e88c4540bf514a70439b57ada47c2c26e24fd57e15a0a7c336e5c0cd10fe1b78d74f54f056
0 commit comments