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
Is your feature request related to a problem? Please describe. It is hard to debug when don't have enough information about what I'm manipulating.
Describe the solution you'd like It would be great to have a logger so that I can see what I'm manipulating in the plugin.
Describe alternatives you've considered Using the DevTools console and making random console.log/console.error in the code.
Additional context Useful links for debugging :
It could be a good idea to implement/integrate a full logger for my plugin ? (using some lib or others).
The text was updated successfully, but these errors were encountered:
Resource for unloading a command in Obsidian : Liam Cain - Unload a Command
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
It is hard to debug when don't have enough information about what I'm manipulating.
Describe the solution you'd like
It would be great to have a logger so that I can see what I'm manipulating in the plugin.
Describe alternatives you've considered
Using the DevTools console and making random console.log/console.error in the code.
Additional context
Useful links for debugging :
It could be a good idea to implement/integrate a full logger for my plugin ? (using some lib or others).
The text was updated successfully, but these errors were encountered: