Repository navigation
Formatter merges pipelines (and everything, including documentation comments) in a single row #812
Description
Steps To Reproduce
1.1
return extractId(req).flatMap(cmsID -> service.find(cmsID))
.flatMap(item -> ServerResponse.ok().syncBody(item))
.doOnError(e -> log.debug(e.getMessage()))
.onErrorResume(this::handleError);
1.2
+ " spherical: true,"
+ " query: {"
+ " status: 'publish',"
+ " $or: [{endDate: {$gt: new Date()}}, {endDate: {$exists: false}}]"
+ " },"
- Alt Shift F / cmd k, f
Current Result
1.1
return extractId(req).flatMap(cmsID -> service.find(cmsID)).flatMap(item -> ServerResponse.ok().syncBody(item))
.doOnError(e -> log.debug(e.getMessage())).onErrorResume(this::handleError);
1.2
+ " spherical: true," + " query: {" + " status: 'publish',"
+ " $or: [{endDate: {$gt: new Date()}}, {endDate: {$exists: false}}]" + " },"
Expected Result
do not touch line breaks, please.
...or do not touch line breaks, when line starts with dot
(code, /** doc comments */ )
Reacted by Raşit Ayaz
Activity
vitorvr commentedon Feb 27, 2019
I have the same "issue".
Camel routes like this:
After format:
from(from).routeId("routeID").autoStartup(true).convertBodyTo(String.class, "UTF-8").to(destination);I edited the Formatter in Eclipse and export it. Tried to use to a local path or GitHub URL but no such luck.
fbricon commentedon Feb 27, 2019
You can add
//@formatter:offat the beginning of the region you don't want to be formatted, and add//@formatter:onat the end, to turn it back on.str-ay commentedon Feb 28, 2019
thanks for workaround. 2 extra lines, but should be helpful for me, will try
samba2 commentedon Jun 17, 2019
I have the same issue, the suggested workaround might help but in times of functional Java and Internal DSLs the VS Code auto formatter is actually hardly useful.
Please provide a solution for this. 🙏
rasitayaz commentedon Aug 12, 2021
Still having this issue, no fixes yet?
snjeza commentedon Aug 12, 2021
See #1126 (comment)
dada-hua commentedon Jul 1, 2023
I think you can:
Set false, it may be ok!
robstryker commentedon Nov 2, 2026
I'm going to close this issue as likely fixed with two workarounds (See snjeza's comment and dada-hua). If it's still replicatable please re-open it.