Bug 536988 - [Formatter] Similar Line Wrapping policy has inconsistent behaviors
Summary: [Formatter] Similar Line Wrapping policy has inconsistent behaviors
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.9   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-13 01:36 EDT by Raku Zeta CLA
Modified: 2022-07-29 16:38 EDT (History)
2 users (show)

See Also:


Attachments
formating result (13.79 KB, image/png)
2018-07-13 01:36 EDT, Raku Zeta CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raku Zeta CLA 2018-07-13 01:36:02 EDT
Created attachment 274961 [details]
formating result

While using 'Wrap all elements, indent all but the first element', given the code:

class A extends B, C {}
class A implements B, C {}
class A throws B, C {}

The 'extends' clause correctly considers the 'extends' keyword itself as the first element (same for the 'implements' clause)

However, the 'throws' clause considers the 'throws' keyword WITH B as the first elements.
Comment 1 Mateusz Matela CLA 2018-07-14 16:39:34 EDT
From bug 44493 comment 8 it seems it was a conscious decision, but I'm not sure how valid the reasoning there is.
Comment 2 Eclipse Genie CLA 2020-08-01 17:11:18 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 CLA 2022-07-29 16:38: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.