Skip to content

Add docs for PSES support with non-VSCode clients #1829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
SydneyhSmith opened this issue Jun 15, 2022 · 1 comment · Fixed by #2147
Closed

Add docs for PSES support with non-VSCode clients #1829

SydneyhSmith opened this issue Jun 15, 2022 · 1 comment · Fixed by #2147
Assignees
Labels
Area-Documentation Issue-Enhancement A feature request (enhancement).
Milestone

Comments

@SydneyhSmith
Copy link
Collaborator

@andschwa recently got PSES v3 working with non-VSCode clients #1820
We should better document how to integrate with PSES

@ghost ghost added the Needs: Triage Maintainer attention needed! label Jun 15, 2022
@andyleejordan andyleejordan self-assigned this Jun 15, 2022
@andyleejordan andyleejordan added Issue-Enhancement A feature request (enhancement). Area-Documentation and removed Needs: Triage Maintainer attention needed! labels Jun 16, 2022
@andyleejordan andyleejordan added this to the Committed milestone Jun 16, 2022
@andyleejordan
Copy link
Member

We need to improve the way we actually execute PSES. First off, we need our cmdlet to have smart defaults, because right now it's a super long string you have to get right, and it's requiring absolute paths in some but not all cases. Very annoying. Let's get it as simple as possible, then document, and then maybe propose bundling PSES into PowerShell with a -lsp flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Documentation Issue-Enhancement A feature request (enhancement).
Projects
Status: Done
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants