-
Notifications
You must be signed in to change notification settings - Fork 15
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.
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
Addition of logging for debug purposes #15
Comments
In addition, I suggest recasting some of the more common external module (ie bass, open al) exceptions to something more human readable, in addition to also throwing more exceptions in our internal code. |
I looked into adding debugging, and started doing just that, but when I was researching it I came to the conclusion that just adding a logger would do the trick. It seems like the more standard thing to do and all anyone has to do to take advantage of it is add a few lines of code to their project to direct the handlers. I did this on my own fork. It seems to provide plenty of flexibility. |
Hi there.
I believe that for debug purposes we should log the actions that are occurring in lucia to better debug if needed. For example
In issue #12 We were getting an error where the library could not be found when lucia was initializzing. However we did not know where was the library trying to load from to begin with. This enancement could possibly make our life easier.
I suggest that an optional argument is added to lucia.initialize()
so like:
lucia.initialize(debug=True)
If not true logging will not be performed.
The text was updated successfully, but these errors were encountered: