Nick Mancuso

Depending on the outcome of https://github.com/checkstyle/checkstyle/issues/14542, we can just delete the website doc in this PR as well.

1. I think it would be good to include this README in the directory where the grammar lives. 2. I would like to include more information about when to use...

I should explain why I think that the guide should live in the main repo, and be written in markdown: > We can start from wiki page 1. I (and...

> @nrmancuso any updates here? I think it would be great to have an explanation of updating grammar and adding support for new tokens Hopefully I will get some time...

> For me this nuance is very non intuitive. @nrmancuso , what is your opinion on this? My opinion is that we should extend our docs to mention this, but...

Issue is approved, I am personally not a big fan of telling users how to use their command line, but if we can help save someone some time, I am...

My first thought was to use https://checkstyle.sourceforge.io/config_whitespace.html#OperatorWrap and some suppression for names that do not match, but this check does not accept the `DOT` token, and I am not sure...

From https://github.com/checkstyle/checkstyle/issues/11087#issuecomment-1004812598: > Should be there any violations in this code.. It depends on user config. I had a very simple implementation in mind, which takes advantage of our treatment...

> The only thing I wanted to point out is for this example we could allow the user to specify the class as the builder @rnveach What about a case...

> are you pitching for 2 properties No, just one. Updated above comment to be more specific.