We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
No description provided.
The text was updated successfully, but these errors were encountered:
Discuss here -- should the logging/error-reporting system be exposed through the API?
Sorry, something went wrong.
What would this mean in practice?
I think the library user should be able to set the log level. This should be exposed by the API.
jml::global_log_level(DEBUG);
Should the library users be able to call the logger itself? Probably not. We probably don't need to allow the following.
jml::log(DEBUG, "This is a debug message");
Would the user need or want to access the data of the logs for any reason? Like programmatically check if any warnings have been created?
JakeRoggenbuck
Successfully merging a pull request may close this issue.
No description provided.
The text was updated successfully, but these errors were encountered: