Remove serilog #463
Merged
Remove serilog #463
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of the ongoing enhancements to our project, we have decided to remove Serilog, an integral logging component, from the core structure. This decision is driven by our commitment to flexibility and modularity in the project’s architecture.
Advantages of Removing Serilog:
Enhanced Customizability: By transitioning the logging functionality to a plugin-based approach, we provide users with the flexibility to choose or customize their logging solutions. This change aligns with modern development practices that favor adaptable and user-specific configurations.
Reduced Complexity: Integrating logging as a plugin rather than a core component simplifies the overall architecture of the project. This reduction in complexity makes the system more maintainable and easier to understand for new developers.
Improved Performance: Removing Serilog from the core project can potentially lead to better performance. By offloading logging to a separate module, the core application becomes lighter and more efficient, especially in scenarios where extensive logging is not required.
Modular Updates: With logging handled by a plugin, updates or changes to the logging mechanism can be made independently of the core project. This modular approach ensures that enhancements or bug fixes in logging do not necessitate a full project update, leading to smoother and more continuous development cycles.
Broader Compatibility: A plugin-based logging system opens the door for greater compatibility with various logging frameworks or custom solutions developed by users. This flexibility ensures that our project can seamlessly integrate into diverse environments and use cases.
In conclusion, while Serilog has been a valuable component, its removal and replacement with a plugin-based logging system is a strategic move towards a more flexible, efficient, and user-friendly project structure.