-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add more logging messages #15
Comments
Are you talking about literally every function in the whole crate? I find your project very interesting so I could get to know the project better through this task. Do you have any other advice on how to begin contributing? I've already read |
Ok maybe not every function 😅 - I think I was having some trouble debugging something when I made this issue. To be honest, the point of this is more to encourage new contributors to look round the code (as you noticed) - IMO the place where logging is needed most is the code that handles editing (which currently resides in There currently isn't much contributor advice other than |
Ideally, we'd have
log::trace!
in every function, andlog::debug!
when debug output might be useful.The text was updated successfully, but these errors were encountered: