Use the controls in this area to specify the XML file to process and the script to be executed.
XSLT Script File - in this text box, specify the path to the XSLT Style Sheet file. Type the path manually or click Browse and select the desired file in the Choose XSLT File dialog box, that opens.
Choose XML Input File - from this drop-down list, select the XML input file to be transformed. The list contains all the XML files that have been associated with the chosen Style Sheet via the File Associations functionality. To specify a file, which is not on the list, click Browse and select the desired file in the Choose XML File dialog box, that opens.
Use the controls in this area to configure handling of the script output.
Show in Default Console - select this option to have the output displayed in the normal run console, together with any warnings and error messages from the XSLT transformer, as well as messages generated by the script, e.g. by xsl:message.
Show in Extra Console Tab - select this option to have the produced output displayed in an extra, XSLT Output, tab.
This option is selected by default.
Highlight Output As - select the file type to highlight the output as.
Save to File - select this option to have the output saved directly to a file. In the text box, specify the name of the target file. Type the path to the file manually or click Browse and select the desired file in the Choose Output File dialog box, that opens. If you type the name of a file that does not exist, GoLand will create a file and save the output to it.
Open File in Editor After Execution - select this checkbox to have the file with the output opened in the editor after the script is executed successfully.
Open File in Web Browser After Execution - select this checkbox to have the file with the output opened in the configured Web browser after the script is executed successfully.
Use the controls in this area to create and manage a list of parameters to be passed to the script.
Add - click this button to create a new entry.
Remove - click this button to remove the selected entry from the list.
Name - in this text box, specify the name of the parameter.
Value - in this text box, specify the value of the parameter.
In this tab, configure additional options that are not commonly required in run configurations.
Smart Error Handling
Clear this checkbox to have the console display full error messages including their complete stack traces, when an error occurs during execution.
Select this checkbox to suppress showing staktraces and have the console display only the relevant information about errors.
In this text box, specify optional VM arguments to be passed to the VM where the XSLT script is executed. These can be heap size, garbage collection options, file encoding, etc. If the line of VM arguments is too long, click to expand the textbox and type the text there.
In this text box, specify the working directory to use. Type the path manually or click Browse and select the desired folder in the Working Directory dialog box, that opens.
If no folder is specified in text box, the working directory will be the one where the XSLT script file is located.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup Shift+Alt+F10.
Share through VCS
Select this checkbox to put the run/debug configuration under version control and make it available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml .
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
View and edit the template (that is, the default settings) for the selected run/debug configuration. The templates are displayed under the Templates node and used for newly created configurations.
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Start React Native Bundler: select this option to run the bundler automatically, as part of a running or debugging session. by default, this is done through react-native start. If your application uses Expo, you need to run the development server via the start npm task. To do that, click , then in the Configure React Native dialog, choose npm script and select start from the list.
If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.
Go Command: select to run a Go command before running your program. For example, you can run go generate to generate source code before compilation. In the Edit Go Command Task dialog, you can use auto-completion. Auto-completion supports the following commands generate, vet, test -i. You can use your own commands.
Upload files to Remote Host: select this option to have the application files automatically uploaded to the server according to the default server access configuration.
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)
Show this page
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.
Otherwise, if the checkbox is cleared, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.