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
The event callbacks acceptd by RuntimeFarkle are not an option. I'm talking about integration with a real logging framework. This will allow gathering much deeper insights about Farkle's internal workings. Furthermore, it might even pave the way for localized log messages! This framework has to be fast (i.e. minimal overhead when no logging is enabled), and have an easy-to-use API.
I am leaning towards either logary, or Serilog, or maybe something else.
The text was updated successfully, but these errors were encountered:
The way Farkle logs messages is extremely flexible; it allows any logging framework to integrate, and does that without any support from 3rd-party logging frameworks. Consumers just pass a function that logs the message in any framework they want.
What is more, the logging message type is structural logging at its finest form.
The event callbacks acceptd by
RuntimeFarkle
are not an option. I'm talking about integration with a real logging framework. This will allow gathering much deeper insights about Farkle's internal workings. Furthermore, it might even pave the way for localized log messages! This framework has to be fast (i.e. minimal overhead when no logging is enabled), and have an easy-to-use API.I am leaning towards either logary, or Serilog, or maybe something else.
The text was updated successfully, but these errors were encountered: