yanrongzhen opened a new pull request, #4447:
URL: https://github.com/apache/eventmesh/pull/4447

   Fixes #4443 .
   
   ## Motivation
   
   ### Why should we use Spotless?
   
   When we writing code, we all want to follow a fixed code style, and the IDEs 
we use also have code formatting functions. 
   
   But unfortunately, code formatting needs to be triggered manually by the 
developer, so there will definitely be times when the formatting is forgotten. 
   
   These problems may be corrected through CR, of course, it may not be seen, 
and a certain piece of code has a **bad smell**.
   
   Although a good, unified code style does not improve code performance, even 
if the code style is bad, the code will compile correctly and run the same 
result. But when your code has a good unified style, the code will be more 
beautiful, better readable, and CR can completely ignore the code style.
   
   Spotless is such a tool that lets you not worry about code style, and can 
bind Gradle's life cycle to automatically format code at build time. 
[https://github.com/diffplug/spotless/tree/main](Spotless Github)
   
   ## Modifications
   
   *Describe the modifications you've done.*
   Use `eventmesh_eclipse_formatter.xml` to replace the original formatting 
function of IntelliJ IDEA, which can be formatted at any time during the 
process of writing code, which greatly improves the development efficiency.
   
   - Added gradle spotless plugin
   - Added eventmesh-spotless-formatter, define formatting rules
   - Added formatting support for license headers
   - Initialize and format the entire eventmesh project
   - Compatible with checkstyle
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to