You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not common but a nested/inner class name is allowed to start with a lower case.
Also, I didn't get to read into the code in detail but is the class name stripping just for human readability or it has code logic significance? Seems unnecessary if just for human read. e.g. one might want to know a log message is issued from an anonymous inner class (whose name may be "XyzClass$1"); stripping off the "$1" may not be desired, or even misleading.
The text was updated successfully, but these errors were encountered:
Not common but a nested/inner class name is allowed to start with a lower case.
You are right. However, this is the best heuristic we could find so far. I have never seen any class not starting with an upper case letter in a real world project so far. In tinylog 3, we only strip a nested/inner class name if it starts with a dollar sign or number.
Also, I didn't get to read into the code in detail but is the class name stripping just for human readability or it has code logic significance?
It is mainly for human readability. However, it has also some indirect impact on setting specific severity levels for classes.
Actually, stripping class names is a very demanded feature and should be the default behavior. Nevertheless I could imagine to move the stripping logic to the class placeholder and make it configurable.
tinylog/tinylog-api/src/main/java/org/tinylog/runtime/RuntimeProvider.java
Line 229 in eab5137
Not common but a nested/inner class name is allowed to start with a lower case.
Also, I didn't get to read into the code in detail but is the class name stripping just for human readability or it has code logic significance? Seems unnecessary if just for human read. e.g. one might want to know a log message is issued from an anonymous inner class (whose name may be "XyzClass$1"); stripping off the "$1" may not be desired, or even misleading.
The text was updated successfully, but these errors were encountered: