-
Notifications
You must be signed in to change notification settings - Fork 2
Logging output suggestions #2
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
Comments
Thanks, @imacrayon for these really nice suggestions! "2" I already have in my To Do list, but I didn't know about "1", I will note that. For now, logging is just a pre-created feature for future uses, for example, I am going to add the "undo" command with help of logging. And honestly, I thought that nobody will need the logging feature 😄 so tell me, why do you need the log files? P.s. If the community will be more active I will harry up with further updates👍 |
Ah, so I misunderstood the purpose of the logs. In my case I ran |
Wow, interesting case! 👍 @imacrayon For now, as quick fix you can run command several times (solve some warnings -> run command again), but I am going to add --report option for similar purpose. If you still need help with it now, I think, I can help you to export warnings using php script |
Hi, @imacrayon! Added --report option in
|
Very cool, thanks! |
I'm running this on MacOS, I've installed it through Composer:
chmod
them before I can read them.MarshalIndent
might be the fix?)The text was updated successfully, but these errors were encountered: