intellij-powershell v2.8.0

Added

• Debugger: "verified" status for breakpoints that are successfully set. Thanks to @Fantoom for the contribution.

Changed

• Requirement update: IntelliJ Platform 2024.2 is now the minimal supported version (i.e., a downgrade, meaning we support more versions).
• Update PSScriptAnalyzer from v1.22.0 to v1.23.0.
• Update junixsocket library from v2.10.0 to v2.10.1.

intellij-powershell v2.7.0

Changed

• Requirement update: IntelliJ Platform 2024.2.0.2 is now the minimal supported version
• Update PowerShellEditorServices from v3.18.1 to v3.20.1
• Update junixsocket library from v2.9.0 to v2.10.0
• Update LSP4J library from v0.22.0 to v0.23.0

Added

• Debugger support based on the debugger adapter protocol from PowerShellEditorServices.

  Thanks to @Fantoom for the contribution.

intellij-powershell v2.6.1

Fixed

• #257: pass -NoProfile to PowerShell when detecting its version, to determine the version faster and avoid possible problems caused by shell customizations

  Thanks to @En3Tho for the contribution.

• #259: additionally, pass -NonInteractive argument

intellij-powershell v2.6.0

Changed

• 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

Removed

• The plugin no longer bundles Plaster that was a part of an older PowerShellEditorServices distribution, even though it wasn't used by the plugin.

intellij-powershell v2.5.0

Fixed

• #67: An attribute block before function's param could lead to incorrect indentation
• #102: Formatter breaking the code around unary operators such as -Not and equal signs in command-line arguments
• #183: Redundant multi line comment closing sequence added when user adds newline
• #138: Run configuration template doesn't work

Added

• #184: Support the null-coalescing operator

Changed

• LSP4J library has been updated to v0.3.1
• junixsocket has been updated to 2.9.0

intellij-powershell v2.4.0

Changed

• The lexer and parser were migrated to be auto-generated by the Gradle Grammar-Kit task. We do not expect any changes, but they may happen, so please report any cases of suspicious plugin behavior.

Fixed

• #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.

intellij-powershell v2.3.1

Fixed

• #172: Console output forcibly wraps output to 80 characters
• #160: the exit keyword is now allowed in more positions in the parser
• #166: "Slow operations are prohibited on EDT" report about disk IO on run configuration startup

Changed

• The PowerShell run configuration no longer ignores certain kinds of internal exceptions; they will be properly reported

intellij-powershell v2.3.0

Changed

• The PowerShellEditorServices connection code has been refactored to not cause any UI freezes: everything was moved to background and rewritten to use non-blocking IO as much as possible

Fixed

• #155: cannot start PowerShellEditorServices under the default PowerShell 5 execution policy, Restricted
• #104 (fixed partially): use less restricting flags when opening pipe connections to PowerShellEditorServices

Added

• #144: terminate the language server processes when exiting the IDE (even if the IDE was terminated abnormally)

intellij-powershell v2.2.0

Changed

• Cleaned up a lot of deprecated API usages and warnings (by @VladRassokhin)
• #148: drop Gson and Guava dependencies from the plugin
• #88: fix UI freezes caused by the plugin and migrate all the LSP communication to background threads

Added

• #145: log PowerShellEditorServices output

intellij-powershell v2.1.0

Changed

• The minimal supported IntelliJ version is now 2023.2
• #45: Upgrade PSScriptAnalyzer from 1.17.1 to 1.21.0, thanks to @bergmeister
• #75: Add indents for array elements when formatting, thanks to @VladRassokhin
• #90: Allow for more user interaction with the run configuration in terminal (use PTY when available), thanks to @ZhengKeli
• #89: Allow entering the executables from PATH in the plugin settings, thanks to @ZhengKeli

Fixed

• #124: Support placing function name on next line in function definition, thanks to @VladRassokhin

Added

• #128: The optional error reports are now sent to the Marketplace in newer IDE versions after the user approval