AppCode 2017.3 Help

Copying Code Style Settings

You can define the code styles that differ from the pre-defined ones. These code style schemes are stored in XML files, in the config/codestyles folder under the user home directory.

You can use the created copy for modifying code styles, and for export.

If you select a code style scheme other than Project, then this code style will be saved for a project. Thus you can assign a global (IDE) code style for each project.

To create a copy of code style settings

  1. In the Code Style page, select the desired scheme from the drop-down list, and click manage profiles.
  2. From the drop-down list, select one of the following options:
    • Copy to IDE - select this option to store the selected scheme in a global level.

      AppCode saves the new code style with the specified name in the config/codestyles/<code_style_name>.xml file under the AppCode home directory.

    • Copy to Project - select this option to store the selected scheme in a project level.

      The selected code style is saved in the .idea directory in the file codeStyleSettings.xml.

    • Duplicate - select this option to simply make a copy of the selected scheme and store it in the same level.
  3. In the Scheme field, type the name of the new scheme and press to save the changes.
  4. Apply changes.

AppCode lets you modify existing names of code style schemes, export or import code style settings.

To manage a code style scheme

  1. In the Code Style page, select the desired scheme from the drop-down list, and click manage profiles.
  2. From the drop-down list, select one of the following options:
    • Rename - select this option to change the name of the selected scheme.
    • Export - select this option to export your code style settings to the desired location.
    • Import - select this option to import AppCode XML code style settings, JSCS config file, or Eclipse XML Profile.
  3. In the Scheme field, type the name of the new scheme and press to save the changes.
  4. Apply changes.
Last modified: 27 March 2018

See Also