radFormatter / docs / profiles

Profiles

A profile is a named starting point for configuration. radFormatter ships four built-in profiles. Whatever you pass with -config is overlaid on top of the profile, so you only specify the keys you want to change.

> radFormatter -profile Embarcadero -config team.json source/MyUnit.pas

Omitting -profile uses Default. Every option and its values are described in the configuration options reference; this page summarizes how the four profiles differ and shows each one on the same input.

At a glance

All four leave alignment off and never reshape calls, enums, arrays, or inheritance lists onto separate lines.

The same code under each profile

Given this input:

unit Demo;
interface
uses System.SysUtils, System.Classes;
implementation
procedure Test(A, B: Integer);
begin
  IF A>0 THEN DoIt(A);
  B:=A*2+1;
end;
end.

Default

Conservative. It reindents to a 2-space structure and applies case-arm layout, but preserves your spacing, casing, and line breaks. For the input above — already 2-space indented — the output is unchanged:

unit Demo;
interface
uses System.SysUtils, System.Classes;
implementation
procedure Test(A, B: Integer);
begin
  IF A>0 THEN DoIt(A);
  B:=A*2+1;
end;
end.

Note that IF A>0 keeps its casing and tight spacing, and the single-line if ... then DoIt(A) is left intact. Use Default when you want structural indentation without opinionated reflow.

FormatterExe

Approximates RAD Studio's built-in Formatter.exe: active spacing, blank lines around sections, begin-style control bodies, uppercase directives/numbers, and an 80-column right margin. Keyword casing is left as-is (note IF / THEN stay uppercase):

unit Demo;

interface

uses System.SysUtils, System.Classes;

implementation

procedure Test(A, B: Integer);
begin
  IF A > 0 THEN
    DoIt(A);
  B := A * 2 + 1;
end;
end.

Embarcadero

The Embarcadero Delphi style guide. Like FormatterExe — active spacing, begin-style control bodies, blank lines around sections — plus lowercase keywords and directives (if / then), one uses entry per line, one statement per line (a break after every statement-terminating semicolon), and a 160-column right margin. Unlike FormatterExe, Embarcadero keeps your existing line breaks (the style guide makes no call on un-wrapping), so only the structural forced breaks above reshape the code:

unit Demo;

interface

uses System.SysUtils,
  System.Classes;

implementation

procedure Test(A, B: Integer);
begin
  if A > 0 then
    DoIt(A);
  B := A * 2 + 1;
end;
end.

See the Embarcadero style guide for the full style-guide mapping.

NoOp

Pass-through. Output matches input byte-for-byte (modulo line-ending normalization). Indentation, case-arm structure, and strict mode are all disabled:

unit Demo;
interface
uses System.SysUtils, System.Classes;
implementation
procedure Test(A, B: Integer);
begin
  IF A>0 THEN DoIt(A);
  B:=A*2+1;
end;
end.

Default vs NoOp

For the sample above the two look identical, but they are not the same profile. Default still reindents (indent size 2) and applies case-arm structure, so mis-indented input is corrected. NoOp disables indentation entirely (indent size 0) and turns strict mode off, so it never moves a character.

Two good reasons to reach for NoOp:

Choosing a profile

Whichever you pick, overlay a -config file to adjust individual options; see the configuration options reference.