Skip to content
This repository has been archived by the owner on Jun 25, 2020. It is now read-only.

Refactor logging #260

Merged
merged 1 commit into from
Aug 4, 2015
Merged

Refactor logging #260

merged 1 commit into from
Aug 4, 2015

Conversation

kodfodrasz
Copy link
Contributor

  • Add some type safety instead of magic strings,
  • flush after receiving error message to prevent log data loss
    on crashing on uncaught exceptions

 - Add some type safety instead of magic strings,
   and flush after receiving error message to prevent log data loss
   on crashing on uncaught exceptions
@kodfodrasz
Copy link
Contributor Author

Overall using a proper logging library, like Serilog, with ConsoleLogger output would be a better choice, IMHO.

@laedit
Copy link
Member

laedit commented Aug 4, 2015

Thanks for your PR, that was needed 😃

You are right about the use of a proper logging library, can you create an issue about that so we can start to debate about the library to use?
I have heard only good thing about Serilog but I haven't tested it yet.

laedit pushed a commit that referenced this pull request Aug 4, 2015
@laedit laedit merged commit 6f26330 into Code52:master Aug 4, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants