Bug 276851

Summary:	[toString] setting to use blocks for if-statements not discoverable
Product:	[Eclipse Project] JDT	Reporter:	Dani Megert <daniel_megert>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r
Version:	3.5
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Dani Megert

2009-05-19 06:21:20 EDT

I20090518-2000.

The toString wizard uses clean up preferences to decide whether to always use blocks. This is not discoverable for the user.

Either we add the same option to the dialog as for hash/code equals or we add a new code style setting and adjust the two wizards.

Comment 1 Markus Keller

2009-05-19 08:10:49 EDT

Should be a code style setting.

Comment 2 Eclipse Genie

2020-05-24 20:11:04 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.

Comment 3 Eclipse Genie

2022-05-20 03:10:05 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.

Comment 4 Eclipse Genie

2024-05-10 18:13:08 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.