Skip to content

Conversation

andyleejordan
Copy link
Member

To fix stdio clients, we needed to fix our startup logic so that the PowerShell host was actually started on initialization, not in theonDidChangeConfiguration handler. The previous way it was done only worked because it relied on a quirk of the VS Code client to send that request immediately, which other clients don’t necessarily do. In order to startup sooner though, we need any configuration that’s applicable on startup to be passed across the wire with the initialize request.

Pairs with PowerShell/PowerShellEditorServices#1801

…izationOptions`

To fix stdio clients, we needed to fix our startup logic so that the
PowerShell host was actually started on initialization, not in the
`onDidChangeConfiguration` handler. The previous way it was done only
worked because it relied on a quirk of the VS Code client to send that
request immediately, which other clients don’t necessarily do. In order
to startup sooner though, we need any configuration that’s applicable on
startup to be passed across the wire with the `initialize` request.
@andyleejordan andyleejordan requested a review from a team May 17, 2022 16:00
Copy link
Collaborator

@SeeminglyScience SeeminglyScience left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@andyleejordan andyleejordan merged commit 3959bdf into master May 17, 2022
@andyleejordan andyleejordan deleted the andschwa/stdio branch May 17, 2022 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants