Adds PowerShell language support to IntelliJ-based IDEs.
Requirement update! If you set the plugin to use PowerShell (aka PowerShell Core, as opposed to Windows PowerShell), then PowerShell 7.2.11 is the minimal supported version
The requirements related to Windows PowerShell version are not changed.
#22: the default working directory for a newly created PowerShell run configuration is now the script's parent directory
Configurations created by previous versions of the plugin are unchanged.
#176: Migrate to PowerShell Core by default
If available on the target system, the modern PowerShell will be used be default, if available. Note that only new plugin installations will be affected, due to how we store the plugin settings. If the plugin is already installed, then it will use the previously discovered PowerShell instance.
This is a Windows-only change, because only on Windows there are two PowerShell versions that may coexist.
#229: the PowerShell run configuration will now save all the files before executing
This fixes the cases when the started configuration wasn't using the latest version of an edited script file.
#51: Update PowerShellEditorServices to v3.18.1
PowerShellEditorServices have been updated to the latest v1.22.0
param
could lead to incorrect indentation-Not
and equal signs in command-line arguments#79: Can't detect PowerShell version on Linux.
Thanks to @8ru73u5 for investigation of the issue.
A bit more of IO work during language server connection moved to the corresponding threads, saving some IDE responsibility in rare cases when it could be a problem.
Increased timeout on connecting to the language server; should fix issues on slower computers.
#42: The run configuration now uses terminal encoding (UTF-8 by default).
#17: When the username has a space, the plugin fails to initialize.
exit
keyword is now allowed in more positions in the parserRestricted
PATH
in the plugin settings, thanks to @ZhengKeli