PowerShell / PowerShell/vscode-powershell
Treat dot sourced files as links
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues to ensure it has not already been reported.
Summary
I would like to have an easy way of opening a dot sourced file when I edit a powershell file. If I edit a ps1 file with a line like this:
. C:\powershell\myimport.ps1
I would expect that VS Code would provide me with a simple way of opening the file. It would be nice if both relative and absolute paths were supported
Proposed Design
It could be handled as a link - like the autogenerated links that are created if you write a URL anywhere in an editor window. Or it could be handled by expanding "Go to definition" to handle dot sourced files by opening them. Or just an extra option when right clicking a dot source line.
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
Start by tracing the VS Code extension's existing link handling and Go to Definition support for PowerShell files; the issue names no files or tests. Compare the behavior needed for relative and absolute dot-sourced paths, then verify that a dot-source line provides an actionable way to open the referenced file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100