[$10 Bounty] Ability to categorize and toggle logging on a per-project, or per-context level. #14
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Could do it with context-opening-and-closing-blocks, and additionally optional context parameter on all log functions.
LOG_CONTEXT("JUI");
RESTORE_LOG_CONTEXT();
DEBUG("JUI", "BIG PROBLEM XYZW");
The intent being we can disable logging on dependency packages and just review logs for the current project being developed. If you have further ideas on this please feel free to discuss.
Yeah, I have thought about rehauling jlog to utilize a logging class for better control over this. However it may make it more difficult to just DEBUG("whatever") and trace functions.
I was playing with the idea this morning and realized it wouldn't fit well with what we currently have. I wish it was easier to do tracing from within C++ without macros.
Alternatively, instead of toggling log calls, could logs be filtered out based on pattern matching?
Maaaaaybeee. Although that sounds really hacky
Since the trace string displays which file it came from, could check if, filepath contains "cmake-build-debug/_deps/"
could be optionally filtered with hide_dependency_logs macro or something?
Granted none of this is ideal systems design, but just to get us thru till we rewrite the entire thing at some point down the road.
Nah, we just need to rewrite it.
Again Jlog needs reworked.