Code Style. Puppet
for Windows and Linux
for OS X
Use this page to configure formatting options for Puppet files. View the result in the
Preview pane on the right.
On this page:
Tabs and Indents
|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, RubyMine uses spaces instead of tabs.
- If this check box is selected, the part of indentation defined by the nesting of code blocks,
is made of the tabs and (if necessary) spaces, while the part of indentation defined by
the alignment is made only of 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 selected, then RubyMine will keep indents on the empty lines as if they
contained some code.|
If this check box is not selected, RubyMine will delete the tab characters and spaces.
Click this link to reveal the list of languages to be used as the base for the current language code style.
So doing, only the settings that are applicable to the current language are taken. All the other settings
are not affected.
This link appears in the upper-right corner of the language-specific code style page, when
Click Reset to discard changes and return to the initial set of code style settings.
Language and Framework-Specific Guidelines:
Last modified: 22 March 2017