Bug 582254 - Missing dedicated lambda code style support
Summary: Missing dedicated lambda code style support
Status: NEW
Alias: None
Product: Incubator
Classification: Eclipse Project
Component: e4 (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: E4 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-28 07:49 EDT by fozzy bear CLA
Modified: 2023-07-28 07:49 EDT (History)
0 users

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 fozzy bear CLA 2023-07-28 07:49:50 EDT 
In Eclipse 4.28.0 there's still no decent support for dedicated handling of lamda code styles and fluent API's (like with Streams) for save actions, e. g. leaving simple one-liners unchanged, or line-breaking at each consecutive method call at "." in fluent styles, to keep a tidy and consistent code style and debuggability. 

Either lamda and fluent API code style will get broken horribly by the legacy conventions, or old legacy code and imperative code style will get affected negatively, when trying to improve the situation dedicatetly for either side.

This is a huge problem, when working in projects with lots of legacy code and dedicated code style save actions, while trying to employ new coding styles with lamdas and fluent API's, while at the same time lacking the required dedicated code styling capabilities, to adapt code styles accordingly.