PowerShellEditorServices icon indicating copy to clipboard operation
PowerShellEditorServices copied to clipboard

A common platform for PowerShell development support in any editor or application!

Results 171 PowerShellEditorServices issues
Sort by recently updated
recently updated
newest added

### Summary of the new feature / enhancement This: ![image](https://user-images.githubusercontent.com/15258962/177668095-fd7cded7-5d9f-4055-b9e3-d1970621f2d7.png) Should work the same as this: ![image](https://user-images.githubusercontent.com/15258962/177668045-734a2ed4-edc9-4939-b2d3-2375d024f284.png) ### Proposed technical implementation details (optional) _No response_

Issue-Enhancement
Up-for-Grabs
Area-IntelliSense

…ReadKey provided by the host instead of Console.ReadKey

Just me trying things. So, weird thing, but in the repro for https://github.com/PowerShell/vscode-powershell/issues/3751, while we're in the debugger, things can't print. Like if you run `Get-Process` at the debug prompt...

Get-EditorServicesParserAst will allow for ExpandAlias or other ast features to look at comment blocks or Functions defined. This also addresses an issue with running the Module in Constrained Language Mode.

This is DRAFT. CI will fail because there's no nuget package on nuget.org! This is the bare minimum work that I would do to adopt the hosted analyzer. It already...

@andschwa recently got PSES v3 working with non-VSCode clients https://github.com/PowerShell/PowerShellEditorServices/pull/1820 We should better document how to integrate with PSES

Issue-Enhancement
Area-Documentation

```ps $Role = [pscustomobject]@{ DisplayName = 'thing' accessPackageResourceScopes = [pscustomobject]@{ DisplayName = 'nestedthing' } } $Role Wait-Debugger ``` ![image](https://user-images.githubusercontent.com/15258962/153964608-c3cd2f1b-ea85-4b84-a8c6-4f22dd731cb3.png) The latter watch expression should return null

Issue-Bug
Area-Debugging

We have a bunch of issues around logging to fix: * When we look for logs, what we're expecting is never there * The way we use the logger itself...

Issue-Enhancement
Area-Logging

You can kind of think of it like `.ConfigureAwait(false)` for completion sources. I didn't necessarily need to add it here, it was just a troubleshooting step, *but* we probably should...

Issue-Enhancement
Area-Engine