Bug 564467 - Code completion for setter missing for final fields
Summary: Code completion for setter missing for final fields
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.17   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-19 06:57 EDT by Christian Pontesegger CLA
Modified: 2022-06-22 08:12 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Pontesegger CLA 2020-06-19 06:57:13 EDT
When typing get/set in the editor I get completion proposals for a new getter/setter method on available fields.

When a field is final, I do not get a setter proposal. This makes sense as final fields do not have setters. But often 'final' is added automatically (eg as 'on save' action). And when I do want a setter I would have to locate the field declaration, remove 'final' jump back to where I want my setter to be located in the source file and add the setter.

It would be great if there would be a proposal for such setters too. Ideally they would remove the final keyword automatically, but that could also be handled via the quick fix.
Comment 1 Eclipse Genie CLA 2022-06-22 08:12:06 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.