Use this page to manage live templates and their settings. (A live template is a code fragment pattern that can be quickly inserted in the editor as a whole. For example, there are live templates for the
UPDATE TABLE and other SQL statements.)
On this page:
- List of available live templates
- Context menu of a live template
- Template editing area
- Predefined functions to be used in live template variables
List of available live templates
|Item||Tooltip and shortcut||Description|
|By default expand with||Use this drop-down list to specify the default invocation key for all templates. Individual expansion keys for the particular templates are defined in the editing area. |
If the standard expansion keys (Tab, Enter, or Space) are not desirable, select the Custom option from this drop-down list.
When Custom is selected, the Change link appears next to the drop-down, leading you to the Keymap page.
|Live Templates||This list shows all currently available template abbreviations supplied with their descriptions. The abbreviations are grouped below nodes and sorted alphabetically within each group. To activate a template or an entire group, select the checkbox to its left.|
|Click this button to have a new template item added to the current group of template. You can define the template abbreviation, description, text, variables, expansion key, and context in the editing area below.|
|Click this button to have the selected live template removed from the list.|
|Duplicate||Click this button to create a new template based on the selected template. A new template item is added to the current node and the fields in the Template Text area show the definition of the selected template.|
|Restore||Click this button to restore the deleted live templates. This button is only enabled when the changes are applied.|
Context menu of a live template
|Move||Choose a group to move the selected template to.|
|Change context||Choose this command to modify the set of contexts where the current template is enabled. Upon choosing this command, a list of supported language contexts is displayed. To make DataGrip consider a context sensitive to the template, select a checkbox next to the context name. |
The available context types depend on the enabled plugins.
|Copy||Choose this command to create a serialized template XML in the system clipboard.|
|Paste||Choose this command to paste an XML representation of the copied templates to the selected group of templates.|
|Restore defaults||This command only appears on the context menus of the modified templates, marked blue. Choose this command to restore the default template settings.|
Template editing area
The focus is moved to this area in the following cases:
- When you click the Add or Copy button.
- When you select a live template in the list.
- When you select a fragment of code in the editor and choose .
Use controls of this area to create new live templates and edit the settings for the existing ones.
You can navigate through the Template Text Area using the hot keys that are marked in the field labels.
|Abbreviation||In this text box, specify the template abbreviation, i.e a sequence of characters that identify the template in the editor.|
|Description||In this text box, provide optional description of a template or an example of its usage.|
|Template Text||In this text box, type the template body that may contain plain text and variables in the format |
|Applicable in:||This read-only field shows the languages and/or pieces of code where the editor should be sensitive to the template. Upon pressing Ctrl+J in such context, DataGrip displays a list of templates that are valid for this context.|
|Change||Click this link to modify the set of contexts where the current template is enabled. Upon clicking the link, a list of supported language contexts is displayed. To make DataGrip consider a context sensitive to the template, select a checkbox next to the context name.|
|Edit Variables||Click this button to open the Edit Template Variables dialog box, where you can define how DataGrip should process template variables upon template expansion. The Edit Template Variables dialog box contains a complete list of available functions. See the list of predefined functions below on this page.|
|Options||In this area, define the behavior of the editor when a template is expanded. |
Predefined functions to be used in live template variables
| Converts a string into camelCase. For example, |
|Capitalizes the first letter of the parameter.|
| Capitalizes all the letters of a CamelCase name passed as the parameter, and inserts an underscore between the parts. For example, |
|Invokes code completion at the position of the variable.|
|Invokes smart type completion at the position of the variable.|
Returns the current system date in the specified format.
Without a parameter, the current date is returned in the default system format.
|Replaces the first letter of the parameter with the corresponding lowercase letter.|
|Returns a list of comma-separated strings suggested for completion when the template is expanded.|
|Escapes the string specified as the parameter.|
|Returns the expected type of the expression into which the template expands. Makes sense if the template expands in the right part of an assignment, after |
|Returns the name of the current file with its extension.|
|Returns the name of the current file without its extension.|
|Returns the first word of the string passed as the parameter.|
|Returns the current line number.|
| Converts a camelCase string into lower case and inserts n-dashes as separators. For example, |
| Converts a string into snake_case. For example, |
| Converts a string into lowercase and inserts spaces as separators. For example, |
| Removes the extension after the specified delimiter and returns only the file name. This is helpful for test file names (for example, |
|Returns the current system time in the specified format.|
| Replaces underscores with camelCase letters in the string passed as the parameter. For example, |
| Replaces underscores with spaces in the string passed as the parameter. For example, |
|Returns the name of the current user.|