On Sun, Mar 29, 2020 at 2:27 PM Saransh Sharma <[email protected]> wrote:
> I think for now it answer the question. Could be great if we can add a > command line tool so that we can quickly apply those config easily without > going to IDE or as you know it might be possible but adding this as a part > of commit. > I see what you mean, but as far as I know, there is no such general tool which just auto applies a CS XML config to .java files... CS wsa written as a "checker" (analysis) not "reformatter" tool. I seems like a great idea, but would likely be a very significant new project (for https://checkstyle.org, no Fineract). -- There may be some other tools for doing what you are after for a subset of our CS rules; I think I once saw something like that specifically for just transparently doing import statement re-ordering during the build (but I forgot what it was called). On Sun, 29 Mar 2020, 17:49 Michael Vorburger, <[email protected]> wrote: > >> Saransh, >> >> On Tue, Mar 3, 2020 at 7:50 AM Saransh Sharma <[email protected]> >> wrote: >> >>> When using eclipse plugin , checkstyle intentionally showing files in >>> the IDE as incorrect but when running from gradle task such as build it >>> simple ignore those. >>> >>> Scenarion 1: >>> >>> When developing and adding new files, does it check for the files and >>> implement the changes, did not happen when I did without the checkStyle >>> settings applied in the eclipse . >>> >> >> does https://github.com/apache/fineract/#checkstyle help answer this? If >> not, how could we make that clearer? >> >> >>> Scenario 2: >>> >>> This could lead to confusion when some one writing new codebase IDE is >>> showing a lot of warnings. >>> >>> I am sure there is no such documentation available as of yet about how >>> to setup and use checkStyle >>> >>> I was wondering, if say we wrote some lines of incorrect code according >>> to checkStyle: can we implement a feature where one can simply run applyALL >>> and it should correct indentation and spaces and imports and so so . >>> >> >> as far as I know, there is no command line tool which auto formats >> sources to comply to Checkstyle, but the IDE configuration metioned above >> gives pretty much the same effect / result. >> >> >>> I am getting this inspiration from the nodejS projects where a single >>> lint file does all the magic and in fact the IDE's pick it up on its own , >>> now given this is a JAVA project its going to be complicated. >>> >>> So any feedback and suggestions , so that we can improve all the process. >>> >>> -- >>> >>> Saransh Sharma >>> *Research Partner* >>> *Muellner Internet Pvt Ltd * >>> >>> >>> ---------------------------------------------------------------------------------------------- >>> >>> The idea of separation of me and you is amazing. >>> >>> ---------------------------------------------------------------------------------------------- >>> *Company Website <https://www.muellners.com/> **Company Linkedin >>> <https://www.linkedin.com/company/muellners> * >>> Company Facebook <https://www.facebook.com/muellners> >>> >>> This mail is governed by Muellner® Internet Private Limited's IT >>> policy. >>> The information contained in this e-mail and any accompanying documents >>> may contain information that is confidential or otherwise protected from >>> disclosure. If you are not the intended recipient of this message, or if >>> this message has been addressed to you in error, please immediately alert >>> the sender by reply e-mail and then delete this message, including any >>> attachments. Any dissemination, distribution or other use of the contents >>> of this message by anyone other than the intended recipient is strictly >>> prohibited. All messages sent to and from this e-mail address may be >>> monitored as permitted by applicable law and regulations to ensure >>> compliance with our internal policies and to protect our business. E-mails >>> are not secure and cannot be guaranteed to be error free as they can be >>> intercepted, amended, lost or destroyed, or contain viruses. You are deemed >>> to have accepted these risks if you communicate with us by e-mail. >>> >>
