Convert to Lambda: manuelle AST-Traversal statt JDT-Refactoring #36
Labels
No labels
bug
build
enhancement
headless
P1-critical
P2-high
P3-medium
P4-low
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-tools/jdt-mcp-server#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
convertToLambda()baut die Lambda-Expression manuell per StringBuilder und ersetzt den Source-Text direkt. JDT hat eine interneConvertAnonymousToLambdaRefactoringdie das sauberer macht.Betroffener Code
RefactoringTools.javaZeilen 1223-1356Vorgeschlagener Fix
JDT-interne Refactoring-Klasse nutzen oder zumindest ASTRewrite verwenden statt String-Manipulation.
Kontext
Identifiziert bei der Architektur-Analyse.
Gefixt in Branch
fix/43-refactoring-errors:ASTRewrite+LambdaExpressionAST-NodesASTNode.copySubtree()für korrektes Kopieren von Body-Expressionsrewrite.replace()statt manueller String-ErsetzungCommit:
8084c7d