| Summary: | [extract interface] does not change references in Maps and Lists [refactoring] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Manuel Wilde <manuel.wilde> |
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | benno.baumgartner, dirk_baeumer, robin.rosenberg |
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
Manuel Wilde
Manuel, do you refer to references like List<TypeToExtractAnInterfaceFrom> ? Tobias, can you please comment. If you are referring to parameterized types: this is currently not implemented. If not, could you please give a code snippet or attach a project which exhibits the defect? From Manuel Wilde <manuel.wilde@kgu-consulting.de> Map<DcAttributeName, AttachedAttributeImpl> attachedAttributes = new LinkedHashMap<DcAttributeName, AttachedAttributeImpl>(); I extracted an Interface from AttachedAttributeImpl and named it AttachedAttribute but the reference in the Map and the linked HashMap was not replaced. Tobias, is this something we can look at for 3.2 ? Sure, we decided to skip that in 3.1 for time reasons, but the existing infrastructure can be easily extended Not for 3.3 not for 3.4 A larger example is to grab https://git.eclipse.org/r/#/c/7283/, go to the Repository class and select extract a new interface from the refactoring menu. It will do wrong in quite a number of places. -All javadoc references seems unchanged, and wrong -Some simple references --fields in DumbClientSmartServerTest are unchanged --Constructor arguments in Git Only a few of these errors are expected This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |