In the Project tool window, the currently loaded stubs are displayed under the External Libraries node. For details on configuring interpreters, see Configure local PHP interpreters and Configure remote PHP interpreters. To load the set of stubs that matches the set of loaded extensions for the currently configured CLI interpreter, click the Sync Extensions with Interpreter button. Use the checkboxes next to each item to enable/disable the corresponding stub. PHP stubs are added to PhpStorm's internal knowledge to enhance coding assistance for all the Standard PHP Library components as well as for common extensions. The area lists the available PHP stubs, which are normal, syntactically correct PHP files containing annotated function, method, and class signatures, constant definitions, and so on. Use and to reorder the items in the list.Ĭlick to sort the paths alphabetically in the ascending order.
Php language code#
Include paths are used for holding third-party code that is used for completion and reference resolution in some functions/methods that use file paths as arguments, for example, require() or include(). The area displays the list of configured include paths. Path mappings cannot be set for project files or folders that are marked as excluded. To remove a custom mapping, select it in the list and click. Type the paths manually or click and select the relevant files or folders in the dialog that opens. To add a custom mapping, click and specify the path in the project and the corresponding path on the remote runtime environment in the Local Path and Remote Path fields respectively. To provide the custom mappings, click next to the field and specify them in the Edit Project Path Mappings dialog that opens:
When you configure a remote interpreter accessible through SFTP, Vagrant, Docker, or WSL this read-only field shows the path mappings retrieved from the corresponding deployment configuration, Vagrantfile, or Dockerfile. See Configure local PHP interpreters and Configure remote PHP interpreters for details. See Configure local PHP interpreters and Configure remote PHP interpreters for details.Ĭlick this button next to the CLI Interpreter list to create a new PhpStorm-wide PHP installation configuration in the CLI Interpreters dialog that opens. The list contains all the currently configured local and remote PHP interpreters. In this list, choose the PHP interpreter to use in the current project by default. The list is inactive when the PHP language version is constrained in composer.json and settings synchronization with composer.json is enabled on the Composer page of the Settings dialog ( Ctrl+Alt+S). You can also set the PHP language level directly from the status bar. When you open an existing project, PhpStorm analyzes it for the language features used and sets the appropriate language level automatically.
However, if you attempt to use a code construct that is not supported by the specified language level, PhpStorm suggests a Switch to PHP quick-fix. Although the language version of each interpreter is detected automatically, you can still tell PhpStorm to provide you with coding assistance that corresponds to a different language level.
No correlation between the PHP version used in the project and the language level is enforced. Each functionality scope is associated with the PHP version that supports this functionality. In this list, specify the PHP functionality scope to get coding assistance for.
0 kommentar(er)
