Bug 345896 - [quick assist] 'Source > Generate constructor using fields' could be a quick assist
Summary: [quick assist] 'Source > Generate constructor using fields' could be a quick ...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 147838 461417 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-16 04:41 EDT by Deepak Azad CLA
Modified: 2015-04-01 08:10 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Deepak Azad CLA 2011-05-16 04:41:00 EDT 
After writing a new field, I generally want to create getters,setters and/or a constructor. 'Source > Getters and Setters' is available as a quick assist, but 'Source > Generate constructor using fields' is not.

When the quick assist is invoked
- if the selection is non zero and contains lets say 3 fields out of a total 4, then in the 'Generate constructor using fields' dialog only these 3 fields should be selected (user can of course change his selection in the dialog)
- if there is no selection then all fields should be selected in the dialog
Comment 1 Glenview Jeff CLA 2011-07-31 10:12:57 EDT 
I'm not sure if this is the same request or just closely related, but I'd like to be able to use quick assist to execute the "generate constructor using fields" in response to "The blank final field foo may not have been initialized" errors.
Comment 2 Markus Keller CLA 2012-02-01 10:13:01 EST 
The quick assist should only be active when a single field is selected and the field is not yet initialized in existing constructors/initializers.
Comment 3 Noopur Gupta CLA 2015-04-01 08:10:25 EDT 
*** Bug 147838 has been marked as a duplicate of this bug. ***
Comment 4 Noopur Gupta CLA 2015-04-01 08:10:48 EDT 
*** Bug 461417 has been marked as a duplicate of this bug. ***