File and Code Templates

Choose whether file and code template settings pertain to the entire workspace, or the current project:

• Default scheme is selected, when file and code templates are global.

• Project scheme is selected, if you want to use the sharable project-specific file and code templates.

This tab displays the available file templates.

You can edit the existing templates, or create new ones.

This tab shows the templates for reusable fragments that can be included in file templates.

You can edit the existing templates, or create new ones.

This tab displays built-in snippets — templates for code fragments that GoLand can generate in various typical situations, for example, for generating implemented or overridden method bodies.

You can edit the existing snippets, but you cannot create new ones.

Click this button to create a new template in the currently opened tab. This option is only available in the Files and the Includes tabs.

The location of the new template is defined by the Schema list.

Edit the template contents. You can use:

• Plain text.

• #parse directives to work with template includes.

• Custom variables. Variables' names can be defined either directly in the template through the #set directive or during the file creation.

  Note that GoLand doesn't prompt for the values of Velocity variables defined with #set.

• Variables to be expanded into corresponding values in the ${<variable_name>} format.

  The following predefined variables can be used in file templates:

  Variable	Description
  ${GO_PACKAGE_NAME_WITH_TEST_SUFFIX}	Name of the package in which the new file is created if it's just regular file and package + '_test' suffix if the new file is a test file
  ${GO_PACKAGE_NAME}	Name of the package in which the new file is created
  ${DATE}	Current system date
  ${DAY}	Current day of the month
  ${DAY_NAME_SHORT}	First three letters of the current month name (Mon, Tue, and so on)
  ${DAY_NAME_FULL}	Full name of the current day (Monday, Tuesday, and so on)
  ${DIR_PATH}	Path to the directory of the new file (relative to the project root)
  ${DS}	Dollar sign $. This variable is used to escape the dollar character, so that it is not treated as a prefix of a template variable.
  ${FILE_NAME}	Name of the new file
  ${HOUR}	Current hour
  ${MINUTE}	Current minute
  ${SECOND}	Current second
  ${MONTH}	Current month
  ${MONTH_NAME_FULL}	Full name of the current month (January, February, and so on)
  ${MONTH_NAME_SHORT}	First three letters of the current month name (Jan, Feb, and so on)
  ${NAME}	Name of the new entity (file, %class%, interface, and so on)
  ${ORGANIZATION_NAME}	Name of your organization specified in the project settings(Ctrl+Alt+Shift+S)
  ${PRODUCT_NAME}	Name of the IDE (for example, GoLand)
  ${PROJECT_NAME}	Name of the current project
  ${TIME}	Current system time
  ${USER}	Login name of the current user
  ${YEAR}	Current year

  Treating dollar sign

  • You can prevent treating dollar characters $ in template variables as prefixes. If you need a dollar character ($ inserted as is, use the ${DS} file template variable instead. When the template is applied, this variable evaluates to a plain dollar character $.

    Examples:

    • To use some version control keywords (such as $Revision$, $Date$, and so on) in your default class template, write ${DS} instead of the dollar prefix $.

    • The template code ${DS}this will be rendered as $this.

Select this checkbox, to have GoLand reformat generated stub files according to the style defined on the Code Style page.

This option is only available in the Files tab.

Select this checkbox to use a live template inside a file template. In doing so, one has to put the live template fragments into Velocity escape syntax.

For example:

Thus, one can specify the cursor position. Note that it is required to use the live template variables here!

This read-only field provides information about the template, its predefined variables, and the way they work.

This field is not available in custom templates.