Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341056 - Quick fix to add/remove method parameter does not respect code formatter settings
Summary: Quick fix to add/remove method parameter does not respect code formatter sett...
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-27 08:10 EDT by Rüdiger Herrmann CLA
Modified: 2019-10-03 12:29 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rüdiger Herrmann CLA 2011-03-27 08:10:46 EDT
The quick fix to add parameters to a method does no respect code formatter settings.
To reproduce:
* create a method void foo() { ... }
* call the method like this: foo( 0 );
* use the quick fix: Change method foo(): add parameter int i
* the method foo() is changed to foo(int i)
-> the refactoring does not insert white space characters after opening and before closing parenthesis. Expected outcome would be: 
  void foo( int i )

When having quick fix remove the last parameter of a method, it leaves an unwanted space between empty parenthesis like so:
  void foo( )
  
The formatter settings are set to have white space after opening parenthesis and before closing parenthesis.
Comment 1 Olivier Thomann CLA 2011-03-30 09:29:25 EDT
Could you please specify the build id ?
Thanks
Comment 2 Rüdiger Herrmann CLA 2011-03-30 13:04:39 EDT
(In reply to comment #1)
> Could you please specify the build id ?
> Thanks
The build id with which I tested was 20100617-1415
Comment 3 Eclipse Genie CLA 2019-10-03 12:29:59 EDT
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.