This feature is supported in the Professional edition only.
for Windows nd Unix
code verifier and configure its behaviour.
Select this check box to have JSHint applied to verify the code in the current project. After that the other controls in the page are enabled.
Use config files
Select this check box to have the code verified according to the settings from a configuration file.
A configuration file is a JSON file with the extension |
.jshintrc that specifies which JSHint options should be enabled or disabled.
PyCharm will look for a
.jshintrc file in the working directory. If the search fails, PyCharm will search in the parent folder, then again in the parent folder.
The process is repeated until PyCharm finds a
.jshintrc or reaches the project root. To have PyCharm still run verification in this case,
specify the default configuration file to use.
Starting with PyCharm version 6.0.1, the globals setting in
.jshintrc is supported.
For earlier versions, a Predefined (, separated)" tree node is displayed in the bottom of the tree in the UI.
When this check box is selected, the Options area is hidden and the default verification settings are unavailable.
Use this drop-down list to choose the version of the tool to apply.
PyCharm comes bundled with version 1.0.0, which is used by default.
PyCharm provides the ability to download another version, which is not bundled. Actually, the alternative version is downloaded only once, whereupon it is available without download.
In this area, configure JSHint behaviour by enabling or disabling JSHint options.
To enable or disable an option, select or clear the corresponding check box respectively.
The controls in the area fall into two groups:
Relaxing options: select/clear the check boxes in this area to suppress warnings when certain types of discrepancies are detected.
Environments: select/clear these check boxes to specify for which environments you want global properties predefined.
The area is available only when the Use config files check box is cleared.
Language and Framework-Specific Guidelines:
Last modified: 25 March 2017