GSoC first issues
Update all javadoc for AST to have different examples, we have some the same https://github.com/checkstyle/checkstyle/pull/13991#pullrequestreview-1829807750
-
[first issue] update AST docs to have examples for all tokens. add
@sinceas it is our API. https://checkstyle.org/apidocs/com/puppycrawl/tools/checkstyle/api/TokenTypes.html , we need to review all and make exact issues. If blame does not show history when it was added, put "4.0" as it is oldest commit we see and dealing with accuracy further in history does not make sense. We should have one issue to put on all tokens 4.0 that are referenced in this oldest commit. -
[first issue] update https://checkstyle.sourceforge.io/apidocs/com/puppycrawl/tools/checkstyle/api/TokenTypes.html to new format of AST print. Example of bad https://checkstyle.sourceforge.io/apidocs/com/puppycrawl/tools/checkstyle/api/TokenTypes.html#PARAMETERS , there might be more, ABSTRACT, STRICTFP, LITERAL_NEW, SINGLE_LINE_COMMENT. (I reviewed all) - will be done at https://github.com/checkstyle/checkstyle/issues/14516
-
[first issue] update https://checkstyle.sourceforge.io/apidocs/com/puppycrawl/tools/checkstyle/api/JavadocTokenTypes.html to new format of AST print.
|--SEE_LITERAL[3x0] : [@see]should be something like|--SEE_LITERAL --> @see
- [second ] (already created issue) update all Inputs to have message for violation (even in Check there is single message, as message might be misleading or weird)
-
[third] migration to Truth in unit tests. Are we done ? we did a lot at the end of year. Any minor refactoring is fine for students as main goal is to make sure they can operate by git/Github/builds
-
update tests to use Input based testing only or put a comment why it is not possible. We should come to state that pure unit test is explained by comments.