-
Notifications
You must be signed in to change notification settings - Fork 641
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
[Enhancement] Optimizing Log Printing Using the LogUtils #4502
Comments
i will try this |
@scwlkq Welcome to EventMesh community, my friend! |
@scwlkq Welcome to EventMesh community! |
Hi, I'm new to open source and want to try to solve some simple problems. Can you assign this issue to me? I would appreciate it! |
Hello, I am also a newcomer to the community. I have previously claimed this task. In fact, I have already written about it, and the code volume is a bit large. |
* Change the log mode to LogUtils * check code style * recheck * fix some code style inappropriate places * temp store * fix merge conflict * final check * fix some field sequence problems and redundant indention problems * Remove unnecessary parameters from the log * fix merge conflict * fix merge conflict * fix merge conflict * correct code style * fix ci * add missing {} in some log statements * fix ci
Search before asking
Enhancement Request
Currently in the project, most places determine whether to print logs through conditional checks. Now there is a common utility class LogUtils to handle these conditional checks. This makes the code look much simpler.
Describe the solution you'd like
current situation
After settlement
Note: Developers need to judge whether each place needs to be changed. For example, some prints are mandatory and do not need conditional checks, so there is no need to change them.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: