Databases
StackOverflow2013
Postsdbo
POEclipse formatter settings for the Builder pattern
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POEclipse formatter settings for the Builder pattern
    primarykey
    data
    text
    <p>I'm extremely frustrated with the Eclipse formatting rules for a series of qualified invocations (i.e., the Builder pattern style). For example, here is my preferred formatting for some code that creates a new Apache Commons CLI <code>Options</code> object:</p> <pre><code> Options options = new Options() .addOption(OPTION_HELP_SHORT, OPTION_HELP, false, "print usage information") .addOption(OPTION_VERSION_SHORT, OPTION_VERSION, false, "print version and exit") .addOption(OptionBuilder.withLongOpt(OPTION_PROPERTIES) .hasArg() .withArgName("FILE") .withType(File.class) .withDescription("specify a user properties file") .create()); </code></pre> <p>I.e., parameters are wrapped and indented if necessary and all qualified invocations except the first, unless necessary, are wrapped and indented if there is more than one. If a parameter list wraps inside a qualified invocation, the invocation should wrap first.</p> <p>The default formatting in Eclipse ("Wrap only when necessary" for arguments and invocations) yields the following mess:</p> <pre><code> Options options = new Options().addOption( OPTION_HELP_SHORT, OPTION_HELP, false, "print usage information") .addOption(OPTION_VERSION_SHORT, OPTION_VERSION, false, "print version and exit").addOption( OptionBuilder.withLongOpt(OPTION_PROPERTIES).hasArg().withArgName( "FILE").withType(File.class).withDescription( "specify a user properties file").create()); </code></pre> <p>Going into "Java Code Style -> Formatter -> Line Wrapping" and the line wrapping setting to "Wrap all elements, except first element if not necessary" for invocations yields:</p> <pre><code> Options options = new Options().addOption( OPTION_HELP_SHORT, OPTION_HELP, false, "print usage information") .addOption(OPTION_VERSION_SHORT, OPTION_VERSION, false, "print version and exit") .addOption( OptionBuilder.withLongOpt(OPTION_PROPERTIES).hasArg().withArgName( "FILE").withType(File.class).withDescription( "specify a user properties file").create()); </code></pre> <p>I don't like that the <code>OptionBuilder</code> expression isn't being wrapped, or that <code>"FILE"</code> gets wrapped without also wrapping <code>withArgName</code>.</p> <p>Changing the indentation to "Indent on column" yields:</p> <pre><code> Options options = new Options().addOption(OPTION_HELP_SHORT, OPTION_HELP, false, "print usage information") .addOption(OPTION_VERSION_SHORT, OPTION_VERSION, false, "print version and exit") .addOption( OptionBuilder.withLongOpt( OPTION_PROPERTIES) .hasArg() .withArgName("FILE") .withType(File.class) .withDescription( "specify a user properties file") .create()); </code></pre> <p>The is breaking the lines where I'd prefer, but pushing things over much too far to the right.</p> <p>Is there any way to convince Eclipse to apply my preferred formatting style or something closer to it than any of the above?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Conway
    1. USChris Conway
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POEclipse formatter settings for the Builder pattern
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POEclipse formatter settings for the Builder pattern
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POEclipse formatter settings for the Builder pattern
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 Good question. I'd like this as well, working a lot with Google Protobufs.
      singulars
      1. POEclipse formatter settings for the Builder pattern
      1. USJesperE
    2. COIt's fixed on 3.6M7!
      singulars
      1. POEclipse formatter settings for the Builder pattern
      1. USnanda
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload