-
-
Notifications
You must be signed in to change notification settings - Fork 964
Configure Exception storage #88
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
Functionality for this is already outlined in the README, we just need to implement it properly. @akalongman Was this code already in the project at some point and then removed? Also, this should include verbosity, which would need more details as to what levels there will be and what is logged in each level. |
Should the exceptions be saved in the same file as the normal logs? I was thinking that it might make sense to leave the exception logging as it is, so that we can simply ask somebody who is having issues, to post the file What do you think? |
Exceptions should not be logged to the same file.. |
Thank for the suggestion @christianromeni ! We plan to implement this in the next release 0.30 |
I don't understand why exception logging is required. |
@ivanbaldo can you show me an example? |
In https://github.com/akalongman/php-telegram-bot/blob/master/examples/hook.php there is a catch block and it suggests people to log them there. |
@ivanbaldo Thanks for point this out, you are right. Feel free to open a pull request to fix it! |
I was going to work into this but found this commit b1184d8 that I think deals with this issue. |
Yes that commit deals with it, you pointed out that the exception file is not the proper place where you have to put the log, so you can move the code in the try catch |
So, this issue should be closed then, commit b1184d8 makes the exception storage optional and configurable. |
closing thanks |
It would be fine to add a method to enable and disable exception log and also to configure the path of the file.
The text was updated successfully, but these errors were encountered: