✏️ Add Trigger Name Prefix and Customizable Hex Color to Logs for Enhanced Clarity and Consistency #53
+21
−2
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.
Add Trigger Name Prefix and Customizable Hex Color to Logs for Enhanced Clarity and Consistency
Description:
This library has been a reliable tool in my workflow, especially in scenarios involving multiple server management. However, a notable limitation is the lack of trigger name prefixes in the logs. This omission complicates log analysis across different servers. To enhance usability, I suggest implementing a feature to prepend the trigger name to each log entry. Additionally, integrating the ability to specify a customizable hex color for each trigger's log output will further improve log clarity. This color consistency will aid in quickly identifying log entries related to specific triggers, making the debugging process more efficient in complex server environments.
Screenshots
Before
After