New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide on logger convention #44

Open

Nightfallstorm opened this issue Dec 16, 2023 · 1 comment

Owner

Nightfallstorm commented Dec 16, 2023

We currently have arbitrary decisions on what kind of logs are debug, trace, info, etc.

We should have a convention to determine which types of log statements are a certain priority.

The text was updated successfully, but these errors were encountered:

Collaborator

alandtse commented Dec 16, 2023

trace - debug stuff that would overwhelm the logs but needed for a specific issue. E.g., keyscan code printing or whatever.
debug - standard debug, for devs and not users. E.g., specific hooks being set
info - stuff for users. E.g., installing "" of hooks. Should probably be SKSEVR or big classes.
warn - Warnings for users to take actions; but no need to stop
error - critical; dll should probably stop

Thoughts? I also have a patch to refine the debug logs to provide more info:

[2023-12-16 02:50:41.277] [info] [67748] [DataHandler.cpp:82] Found VRcompiledFileCollection 0x1be89bb75d0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment