Code Style. JSON
for Windows and Linux
for OS X
Use this page to configure
options for JSON files. View the result in the
Preview
pane on the right.
On this page:
Tabs and Indents
| Item | Description |
|---|
| Use tab character |
-
If this check box is selected, tab characters are used:
- On pressing the Tab key
- For indentation
- For code reformatting
-
When the check box is cleared, PhpStorm uses spaces instead of tabs.
|
| Smart tabs |
-
If this check box is selected, PhpStorm inserts tabs for indentation and reformatting.
PhpStorm inserts tabs in the beginning of each line
until a symbol other than the tab is inserted. After that when you press the tab key,
PhpStorm will enter spaces.
-
If this check box is cleared, only tabs are used. This means that a group of spaces that
fits the specified tab size is automatically replaced with a tab, which may result in
breaking fine alignment.
The Smart Tabs check box is available if the
Use Tab Character check box is selected.
|
| Tab size | In this text box, specify the number of spaces included in a tab. |
| Indent | In this text box, specify the number of spaces (or tabs if the
Use Tab Character
check box is selected) to be inserted for each indent level.
|
| Continuation indent | In this text box, specify the number of spaces (or tabs if the
Use Tab Character check box is selected) to be inserted between the elements
of an array, in expressions, method declarations and method calls. |
| Keep indents on empty lines | If this check box is cleared, then PhpStorm will keep indents on the empty lines as if they have contained some code.
If this check box is not selected, PhpStorm will delete the tabulation characters. |
|
Indent chained methods
|
Use this check box to configure indentation of chained method calls.
|
Spaces
Use this tab to specify where you want spaces in your code. To have PhpStorm automatically insert a space at a location,
select the check box next to this location in the list.
The results are displayed in the Preview pane.
Blank Lines
Use this tab to define where and how many blank lines you want PhpStorm to retain and insert in your code
after reformatting. For each type of location, specify the number of blank lines to be inserted.
The results are displayed in the Preview pane.
| Item | Description |
|---|
| Keep Maximum Blank Lines | In this area, specify the number of blank lines to be kept after reformatting in the specified locations. |
| In code | Use this field to set the number of the blank lines. |
Wrapping and Braces
In this tab, customize the code style options, which PhpStorm will apply on reformatting the source code.
The left-hand pane contains the list of exceptions (Keep when reformatting), and
placement and alignment options for the various code constructs (lists, statements, operations, annotations, etc.).
The right-hand pane shows preview.
Alignment takes precedence over indentation options.
Right Margin (columns)
Use Right Margin field to specify a margin space required on the right side of an
element. If you select Default option then a value of the right margin from the
global settings is used.
Wrap on Typing
Use Wrap on typing settings to specify how the edited text is fitted in the
specified Right margin.
You can select one the following options:
- Default - in this case PhpStorm uses the Wrap on typing option that is specified
in the global settings.
- Yes - in this case PhpStorm uses the value specified in the
Right Margin field.
- No - in this case this option is switched off and a line can exceed
the value specified in the right margin.
Keep When Reformatting
Use the check boxes to configure exceptions that PhpStorm will make when reformatting the source code.
For example, by default, the Line breaks check box is selected. If your code contains lines that are shorter than a
standard convention, you can convert them by disabling the Line breaks check box before you reformat the source code.
Wrapping Options
The wrapping style applies to the various code constructs, specified in the left-hand pane (for example, method call arguments, or assignment statements).
| Item | Description |
|---|
| Wrapping style | From this drop-down list, select the desired wrapping style:
|
| Ensure right margin is not exceeded | If this check box is selected, the formatter will do its best to avoid having document lines exceeding the right margin.
This option takes precedence over the Do not wrap wrapping style. |
Alignment Options
| Item | Description |
|---|
|
Align when multiline |
If this check box is selected, a code construct starts at the same column on each next line.
Otherwise, the position of a code construct is determined by the current indentation level.
|
| Align parenthesised when multiline |
If this check box is selected, a parenthesised code construct starts at the column of the opening
parenthesis each next line. Otherwise, the position of a code construct is determined by the
current indentation level.
|
<character(s)> on next line | Select this check box to have the specified character or characters moved to the next line when the lines are wrapped. |
|
'else' on new line | Use this check box to have the corresponding statements or characters moved to the next line. |
New line after <character>
| Select this check box to have the code after the specified character moved to a new line. |
| Special else if treatment | If this check box is selected, else if statements are located in the same line.
Otherwise, else if statements are moved to the next line to
the corresponding indent level.
|
| Indent case branches |
If this check box is selected, the case statement is located at the corresponding indent level.
Otherwise, case statement is placed at the same indent level with switch.
|
Other
| Item | Description |
|---|
| Align object properties | From the drop-down list, select the type of objects' alignment:
-
Do not align: the attributes in sequential lines will be not aligned.
-
On colon: the attributes in sequential lines will be aligned against the colon.
-
On value: the attributes in sequential lines will be aligned against the value.
|
Last modified: 12 July 2016