Adding missing @Override annotations (part 3). Adding RRA/RWA/RUI annotations. Some localization and refactoring - #13
Conversation
…otations. Some localization and refactoring.
|
@claude review pr with inline comments |
|
Claude finished @unv-unv's task in 4m 33s —— View job PR Review — @OverRide / RRA-RWA-RUI annotations, localization, refactoring
I reviewed all 62 changed files. The bulk of this PR is clean, mechanical, and looks good: adding missing I left 3 inline comments — one worth a real look, two minor:
Everything else looks good to me. 👍 |
|
|
||
| writer.println("input"); | ||
| writer.println(StringUtil.escapeStringCharacters(tag.getText())); | ||
| writer.println(StringEscapeUtil.escape(tag.getText(), '"')); |
There was a problem hiding this comment.
The custom-bean text is sent to the out-of-process parser on a single line (writer.println(...)), and the parser reads it back with input.readLine() and its own decode() — which un-escapes \n, \r, \t, \b, \f, \", \', \\ and \uXXXX (see CustomBeanParser.decode()).
The previous StringUtil.escapeStringCharacters(tag.getText()) escaped newlines/control chars, so a multi-line <bean> tag was collapsed into one line that survives readLine(). If StringEscapeUtil.escape(text, '"') only escapes " (and \) and leaves real newlines intact, then every multi-line tag — i.e. essentially all of them — will break the readLine() framing and parsing will fail.
The mirror-image concern applies to the two StringEscapeUtil.unescape(...) calls (lines 411 and 433), which now decode the parser's encode() output. Please confirm escape/unescape handle the same escape set as the parser's encode/decode; if not, keeping StringUtil.escapeStringCharacters / StringUtil.unescapeStringCharacters here would be safer.
| descriptionTemplate, | ||
| ProblemHighlightType.GENERIC_ERROR_OR_WARNING | ||
| )); | ||
| holder.registerProblem(holder.getManager().newProblemDescriptor(descriptionTemplate).range(element, range).create()); |
There was a problem hiding this comment.
The old implementation passed ProblemHighlightType.GENERIC_ERROR_OR_WARNING explicitly. newProblemDescriptor(...).range(...).create() relies on the builder's default highlight type. Please confirm that default is still GENERIC_ERROR_OR_WARNING, otherwise the severity/appearance of this reported problem changes silently.
| case NONE -> NONE; | ||
| case OBJECTS -> OBJECTS; | ||
| case SIMPLE -> SIMPLE; | ||
| default -> DEFAULT; |
There was a problem hiding this comment.
Minor: case null plus all four DefaultDependencyCheck constants already make this switch exhaustive, so this default -> DEFAULT branch is unreachable. Dropping it turns any future addition to DefaultDependencyCheck into a compile error you must handle explicitly (rather than silently mapping it to DEFAULT):
| default -> DEFAULT; |
|
@claude review pr with inline comments |
|
Claude finished @unv-unv's task in 4m 39s —— View job PR Review — @OverRide / RRA-RWA-RUI annotations, localization, refactoring
The bulk of this PR is clean and mechanical — I re-checked the three items from the earlier pass and traced the parser protocol to a firm conclusion this time:
|
No description provided.