@Loggagle error level for exceptions

[Maze-fr]

Hello,

It would be nice to be able to say to @Loggable that when an exception is thrown, it should log with another level (like ERROR, for example).
Currently, it is logging with the same level as the level defined (so default is INFO).

I explain...
When working on the project, INFO is enough to track what is going on. But when in production, the logging level is probably set to WARN, so when the method fails with an exception, it is logged as INFO and we don't see it.

I think that a lot of people would love to have their method parameters when the method fails with an exception ;-)
And from what I see in MethodLogger.java, it would be very easy to add this new feature.

Thanks

[0crat]

@yegor256/z please, pay attention to this issue

[0crat]

@Maze-fr/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

[0crat]

Job #259 is now in scope, role is DEV

[0crat]

Thanks for your contribution, @Maze-fr/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role DEV is banned at #259; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)