Use this dialog box to define the scope for the search of dependencies or nullable elements. The contents of the dialog boxes slightly differ depending on the type of analysis.
| Item | Description |
|---|---|
| Whole project | Select this option to perform the analysis for the whole project. |
| Module <name> | Select this option to have IntelliJ IDEA analyze the module that is currently selected in the Project tool window. |
| File <name> | Select this option to analyze the file that is currently selected in the Project tool window or opened in the editor. |
| Selected files | Select this option to analyze the files that are currently selected in the Project tool window. |
| Uncommitted files | This scope is only available for the projects under version control. Select this option to have IntelliJ IDEA analyze only files that have not been committed to the version control system. Use the drop-down list to further limit the analysis scope. The available options are:
|
| Custom scope |
Select this option to use a custom scope. Select a pre-defined scope from the drop-down
list, or click  and define the scope
in the Scopes dialog.
Use a special language to define a scope. |
| Include test sources | Select this checkbox to perform analysis on the test sources. |
| Scope of interest | From this drop-down list, select the scope to seek for backward dependencies.
The field is available for the backward dependencies analysis only. |
| Show transitive dependencies. Do not travel deeper than | Select this checkbox to have IntelliJ IDEA analyze transitive dependencies.
From the Do not travel deeper than drop-down list, choose the desired level.
The field is available for the dependencies analysis only. |
| Annotate local variables | If this checkbox is selected, then the local variables of a class will be included in the
nullity analysis, and annotated.
The field is available for inferring nullity only. |