Hi,
I realize I posted the announcement of our first plugin in the support thread. I’ll add it in here as well and turn that thread into discussion / support thread.
We have just released our first plugin, Logger (free). Logger is a plugin that will help troubleshooting and printing information to the app console.
In short Logger will help you with a couple of things
- Structure your logging - Tagging every message with a tag gives structure to the console
- Prioritize by setting appropriate log level for each message
- Filter out irrelevant log messages depending on the situation. Troubleshooting an ads issue, print log level DUMP for ads and WARNING for everything else. No need to remove any log statements.
- Quickly see where things happen (file, method, line number) and how important they are
An example of how you could structure your logging
- Useful basic stuff, like package name and market build, that should always be shown? Use “log” level/severity
- Stuff that you as a developer always want to see, but too much detail for regular user? Use “debug” level
- Detailed / verbose logging that you only want to see if you are digging into a particular part of the code? Use “dump” level
- Things that aren’t that good, and you as a dev need to notice them, but the code will still work? E.g. fail to download a remote config file. Use “warning” level
- Errors which aren’t quite so bad that you want to go down in flames, but still super-important to notice when testing? Use "error” level
Please share your structure, examples and tips in the discussion thread!
Links:
Plugin@marketplace: https://marketplace.coronalabs.com/plugin/logger
Discussion thread: https://forums.coronalabs.com/topic/67603-logger-lua-plugin-to-speed-up-troubleshooting/
Documentation: http://yogergames.gitlab.io/logger/
Email: support@yogergames.com or joakim@yogergames.com