feat: logging system rewrite #10

New issue

Closed

opened 2024-10-30 21:47:48 +01:00 by JeremyStarTM · 1 comment

JeremyStarTM commented

2024-10-30 21:47:48 +01:00

Owner

Feature description

I want the entire logging system to be rewritten.

What we have now is working, but bare bones. It could be much better.

Feature implementation

Instead of the setup we have now, where there is one big Logger class handling logging, one CrashHandler class just for crashes and a LoggerInstance class serving as the middleman, I'd propose instead having multiple classes (e.g. CrashHandler, LoggingProcessor, LoggingThread) for better code separation, repurposing our current LoggerInstance for a regular Logger class having about the same function, making LogRules a bit nicer to work with, and finally, adding a mode to fully disable logging, either for the engine or everything, which would benefit console applications greatly.

Feature alternatives

Staying with the current logging system.

### Feature description I want the entire logging system to be rewritten. What we have now is working, but bare bones. It could be much better. ### Feature implementation Instead of the setup we have now, where there is one big `Logger` class handling logging, one `CrashHandler` class just for crashes and a `LoggerInstance` class serving as the middleman, I'd propose instead having multiple classes (e.g. `CrashHandler`, `LoggingProcessor`, `LoggingThread`) for better code separation, repurposing our current `LoggerInstance` for a regular `Logger` class having about the same function, making `LogRule`s a bit nicer to work with, and finally, adding a mode to fully disable logging, either for the engine or everything, which would benefit console applications greatly. ### Feature alternatives Staying with the current logging system.