In this field, tell PhpStorm where it should search for the tool's output: the resulting source code, source maps, dependencies, or the file itself. If an argument contains double quotes, use backslashes to escape them: -Dmy.prop=\"quoted_value"\. If an argument contains spaces, enclose them or the entire argument in double quotes: some" "arg or "some arg". When specifying the arguments, follow these rules: Type the macros manually or click and select the relevant pattern fom the list in the Macros dialog that opens. In this field, define the arguments to pass to the tool and thus influence its behaviour.Īrguments are usually specified using macros, for example, $FileName$ or $FileNameWithoutExtension$, that will be replaced with the actual filenames. Alternatively, to use a relative path, add its parent folder to the PhpStorm path variables on the Appearance & Behavior | Path Variables page of the IDE settings Ctrl+Alt+S. To use a jar archive, specify the absolute path to it. To use the program filename instead of filename path, add the path to its folder to the system environment variable PATH. bat, or other depending on the specific tool.) In this field, specify the path to the tool's executable file (. In this area, configure interaction with the tool: specify the executable file to use, the arguments to pass to it, and where PhpStorm should look for the tool's output. This option is available only for Babel, Closure Compiler, Jade, Less, Sass/ SCSS, Stylus, and UglifyJS. Otherwise, if the checkbox is cleared, the File Watcher processes both of these files. With the Track only root files checkbox selected, editing another.scss invokes the File Watcher only on root.scss. Note that the Scope setting overrides the Track only root files checkbox setting: if a dependency is outside the specified scope, the File Watcher is not applied to it.Įxample Suppose you have two files root.scss and another.scss where root.scss imports another.scss. When the checkbox is cleared, the File Watcher runs against the file from which it is invoked and against all the files in which this file is included recursively within the specified scope. When this checkbox is selected, the File Watcher runs only against the root files. VCS Scopes: these scopes are only available if your project is under version control.Īll Changed Files: all changed files, that is, all files associated with all existing changelists.ĭefault Changelist: all the files associated with the changelist Default.Īlternatively, click and configure a custom scope in the Scopes dialog that opens.Ī root file is a file that is not included (for example via import) in any other file within the specified scope. Open Files: all the files that are currently opened in the editor.Ĭurrent File: the file opened in the active editor tab. Scratches and Consoles: all the files from the Scratches and Consoles directory located in the Project tool window. Project Test Files: all the files within the project test source roots. Project Production Files: all the files within the project content roots excluding test sources. Project Files: all the files within the project content roots (see Content root and Configuring content roots). For a project-level File Watcher, you can also click to configure a custom scope in the Scopes dialog that opens. Select one of the predefined scopes from the list.
Use this list to define the range of files the File Watcher can be applied to.Ĭhanges in these files will invoke the File Watcher either immediately or upon save or frame deactivation, depending on the status of the Auto-save edited files to trigger the watcher checkbox. File types are recognised based on associations between file types and file extensions.īy default, the field shows the file type in accordance with the chosen predefined template. The File Watcher will consider only files of this type as subject for analyzing and processing. Use this list to specify the expected type of input files.
0 kommentar(er)
