![]() If you are excluding a folder, this action removes only the files located inside this folder. Include Recursively: include the selected folder together with the nested subfolders and their contents.Įxclude: exclude the selected items from the scope. All nested subfolders and their contents will not be included. If you are including a folder, this action adds only the files located inside this folder. Select the necessary items in the project tree and click one of the options located on the right from the tree: In the dialog that opens, name the new scope and click OK.Īdd files to the new scope. You can change the state of the selected scope (local or shared) later using the Share through VCS checkbox. Press Control+Alt+S to open the IDE settings and then select Appearance & Behavior | Scopes.Ĭlick the Add Scope button ( ) and select what kind of scope you want to define: local or shared. In RustRover, there's a set of predefined scopes, but you can also define your own scopes. Project Non-Source Files: this scope corresponds to other project files, for example, resources, licenses, and so on. Project Source Files: this scope corresponds to the files that contain project source code, including programs and tests. Libraries and frameworks generally are not included in this scope. RustRover provides a number of predefined scopes, for example:įiles: this scope includes all files within a project content root. If you want to configure these settings for the current project and for all newly created projects (globally), go to File | New Projects Setup | Settings for New Projects. This page describes how to configure scopes and file colors for a single project. ![]() If you don't use a VCS, local scopes will be sufficient to cover your needs. Using shared scopes makes sense if your project is under version control. xml extension (for example: MyProject/.idea/scopes/shared-scope.xml). These scopes are stored together with the project in the scopes folder under. Shared scopes are added to a VCS so that people who work on a project can use the same scopes. Local scopes are stored in the IDE configuration directory, that is why they are not shared through VCS and are not available to other members of your team. There are 2 types of scopes: local and shared. In RustRover, scopes are used in code inspections, some refactorings, search, in copyright settings, in various features for code analysis, and so on. For example, a custom scope can include only those files in the project for which you are responsible. There, you can include any files and folders. ![]() RustRover comes with a set of predefined scopes, but you can also create custom scopes. For example, running test-related inspections only in test classes takes less time than if you run them in all files in your application. These logical chunks make your project easier to manage. Scopes are designed to logically organize files in your project: test sources can go to the test-related scope, and production code can be associated with the scope of production files. ![]() You can use scopes to visually distinguish project items in different IDE views and to limit the range of specific operations. A scope is a group of files and folders in a project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |