PowerShell / PowerShell/PowerShellEditorServices
LSP support for modules
Open
Nobody has claimed this yet.
Issue-Discussion
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
I'd like to get LSP support for modules I use frequently, like MSOnline.
I copied the modules into my bundle_path, but that doesn't seem to import them into the session of powershell that PSES runs
for context, I'm using neovim LSP running in WSL debian, with these settings:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the issue with the MSOnline modules in bundle_path and the provided Neovim LSP settings under WSL Debian, then trace how PowerShell Editor Services creates its session. Done means frequently used modules are available to the LSP session for module support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, neovim, powershell
- Domain
- developer-experience, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100