|
1 | 1 | # PowerShell Editor Services Release History
|
2 | 2 |
|
| 3 | +## 1.3.2 |
| 4 | +### Monday, June 12, 2017 |
| 5 | + |
| 6 | +- [PowerShell/vscode-powershell#857](https://github.com/PowerShell/vscode-powershell/issues/855) - Typing a new function into a file no longer causes the language server to crash |
| 7 | + |
| 8 | +- [PowerShell/vscode-powershell#855](https://github.com/PowerShell/vscode-powershell/issues/855) - "Format Document" no longer hangs indefinitely |
| 9 | + |
| 10 | +- [PowerShell/vscode-powershell#859](https://github.com/PowerShell/vscode-powershell/issues/859) - Language server no longer hangs when opening a Pester test file containing dot-sourced script references |
| 11 | + |
| 12 | +- [PowerShell/vscode-powershell#856](https://github.com/PowerShell/vscode-powershell/issues/856) - CodeLenses for function definitions no longer count the definition itself as a reference and shows "0 references" when there are no uses of that function |
| 13 | + |
| 14 | +- [PowerShell/vscode-powershell#838](https://github.com/PowerShell/vscode-powershell/issues/838) - Right-clicking a debugger variable and selecting "Add to Watch" now has the desired result |
| 15 | + |
| 16 | +- [PowerShell/vscode-powershell#837](https://github.com/PowerShell/vscode-powershell/issues/837) - Debugger call stack now navigates correctly to the user's selected stack frame |
| 17 | + |
| 18 | +- [PowerShell/vscode-powershell#862](https://github.com/PowerShell/vscode-powershell/issues/862) - Terminating errors in the language server now close the Integrated Console immediately and prompt the user to restart the session |
| 19 | + |
| 20 | +- [PowerShell/PowerShellEditorServices#505](https://github.com/PowerShell/PowerShellEditorServices/issues/505) - Added improved cmdlet help in the PowerShellEditorServices.Commands module |
| 21 | + |
| 22 | +- [PowerShell/PowerShellEditorServices#509](https://github.com/PowerShell/PowerShellEditorServices/issues/509) - Importing the PowerShellEditorServices.Commands module no longer causes errors to be written about missing help languages |
| 23 | + |
| 24 | +## 1.3.1 |
| 25 | +### Friday, June 9, 2017 |
| 26 | + |
| 27 | +#### Fixes and improvements |
| 28 | + |
| 29 | +- [PowerShell/vscode-powershell#850](https://github.com/PowerShell/vscode-powershell/issues/850) - |
| 30 | + Fixed an issue where lower-cased "describe" blocks were not identified by |
| 31 | + the CodeLens feature. |
| 32 | + |
| 33 | +- [PowerShell/vscode-powershell#851](https://github.com/PowerShell/vscode-powershell/issues/851) - |
| 34 | + Fixed an issue where the language server would hang when typing out a describe |
| 35 | + block. |
| 36 | + |
| 37 | +- [PowerShell/vscode-powershell#852](https://github.com/PowerShell/vscode-powershell/issues/852) - |
| 38 | + Fixed an issue where Pester test names would not be detected correctly when |
| 39 | + other arguments like -Tags were being used on a Describe block. |
| 40 | + |
| 41 | +## 1.3.0 |
| 42 | +### Friday, June 9, 2017 |
| 43 | + |
| 44 | +#### Notice of new internal redesign ([#484](https://github.com/PowerShell/PowerShellEditorServices/pull/484), [#488](https://github.com/PowerShell/PowerShellEditorServices/pull/488), [#489](https://github.com/PowerShell/PowerShellEditorServices/pull/489)) |
| 45 | + |
| 46 | +This release marks the start of a major redesign of the core PowerShell |
| 47 | +Editor Services APIs, PSHost implementation, and service model. Most of |
| 48 | +these changes will be transparent to the language and debugging services |
| 49 | +so there shouldn't be any major breaking changes. |
| 50 | + |
| 51 | +The goal is to quickly design and validate a new extensibility model that |
| 52 | +allows IFeatureProvider implementations to extend focused feature components |
| 53 | +which could be a part of PowerShell Editor Services or another extension |
| 54 | +module. As we progress, certain features may move out of the core Editor |
| 55 | +Services module into satellite modules. This will allow our functionality |
| 56 | +to be much more flexible and provide extensions with the same set of |
| 57 | +capabilities that built-in features have. |
| 58 | + |
| 59 | +We are moving toward a 2.0 release of the core PowerShell Editor Services |
| 60 | +APIs over the next few months once this new design has been validated and |
| 61 | +stabilized. We'll produce updated API documentation as we move closer |
| 62 | +to 2.0. |
| 63 | + |
| 64 | +#### New document symbol and CodeLens features ([#490](https://github.com/PowerShell/PowerShellEditorServices/pull/490), [#497](https://github.com/PowerShell/PowerShellEditorServices/pull/497), [#498](https://github.com/PowerShell/PowerShellEditorServices/pull/498)) |
| 65 | + |
| 66 | +As part of our new extensibility model work, we've added two new components |
| 67 | +which follow the new "feature and provider" model which we'll be moving |
| 68 | +all other features to soon. |
| 69 | + |
| 70 | +The IDocumentSymbols feature component provides a list of symbols for a |
| 71 | +given document. It relies on the results provided by a collection of |
| 72 | +IDocumentSymbolProvider implementations which can come from any module. |
| 73 | +We've added the following built-in IDocumentSymbolProvider implementations: |
| 74 | + |
| 75 | +- ScriptDocumentSymbolProvider: Provides symbols for function and command |
| 76 | + definitions in .ps1 and .psm1 files |
| 77 | +- PsdDocumentSymbolProvider: Provides symbols for keys in .psd1 files |
| 78 | +- PesterDocumentSymbolProvider: Provides symbols for Describe, Context, and |
| 79 | + It blocks in Pester test scripts |
| 80 | + |
| 81 | +We took a similar approach to developing an ICodeLenses feature component |
| 82 | +which retrieves a list of CodeLenses which get displayed in files to provide |
| 83 | +visible actions embedded into the code. We used this design to add the |
| 84 | +following built-in ICodeLensProvider implementations: |
| 85 | + |
| 86 | +- ReferencesCodeLensProvider: Shows CodeLenses like "3 references" to indicate |
| 87 | + the number of references to a given function or command |
| 88 | +- PesterCodeLensProvider: Shows "Run tests" and "Debug tests" CodeLenses on |
| 89 | + Pester Describe blocks in test script files allowing the user to easily |
| 90 | + run and debug those tests |
| 91 | + |
| 92 | +Note that the ICodeLensProvider and IDocumentSymbolProvider interfaces are |
| 93 | +not fully stable yet but we encourage you to try using them so that you can |
| 94 | +give us your feedback! |
| 95 | + |
| 96 | +#### Added a new PowerShellEditorServices.Commands module (#[487](https://github.com/PowerShell/PowerShellEditorServices/pull/487), #[496](https://github.com/PowerShell/PowerShellEditorServices/pull/496)) |
| 97 | + |
| 98 | +We've added a new Commands module that gets loaded inside of PowerShell Editor |
| 99 | +Services to provide useful functionality when the $psEditor API is available. |
| 100 | + |
| 101 | +Thanks to our new co-maintainer [Patrick Meinecke](https://github.com/SeeminglyScience), |
| 102 | +we've gained a new set of useful commands for interacting with the $psEditor APIs |
| 103 | +within the Integrated Console: |
| 104 | + |
| 105 | +- [Find-Ast](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Find-Ast.md) |
| 106 | +- [Get-Token](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Get-Token.md) |
| 107 | +- [ConvertFrom-ScriptExtent](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/ConvertFrom-ScriptExtent.md) |
| 108 | +- [ConvertTo-ScriptExtent](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/ConvertTo-ScriptExtent.md) |
| 109 | +- [Set-ScriptExtent](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Set-ScriptExtent.md) |
| 110 | +- [Join-ScriptExtent](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Join-ScriptExtent.md) |
| 111 | +- [Test-ScriptExtent](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Test-ScriptExtent.md) |
| 112 | +- [Import-EditorCommand](https://github.com/PowerShell/PowerShellEditorServices/blob/master/module/docs/Import-EditorCommand.md) |
| 113 | + |
| 114 | +#### Microsoft.PowerShell.EditorServices API removals ([#492](https://github.com/PowerShell/PowerShellEditorServices/pull/492)) |
| 115 | + |
| 116 | +We've removed the following classes and interfaces which were previously |
| 117 | +considered public APIs in the core Editor Services assembly: |
| 118 | + |
| 119 | +- ConsoleService and IConsoleHost: We now centralize our host interface |
| 120 | + implementations under the standard PSHostUserInterface design. |
| 121 | +- IPromptHandlerContext: We no longer have the concept of "prompt handler |
| 122 | + contexts." Each PSHostUserInterface implementation now has one way of |
| 123 | + displaying console-based prompts to the user. New editor window prompting |
| 124 | + APIs will be added for the times when a UI is needed. |
| 125 | +- Logger: now replaced by a new non-static ILogger instance which can be |
| 126 | + requested by extensions through the IComponentRegistry. |
| 127 | + |
3 | 128 | ## 1.2.1
|
4 | 129 | ### Thursday, June 1, 2017
|
5 | 130 |
|
|
0 commit comments