PowerShell / PowerShell/PowerShellEditorServices
Add some form of error/output if $Profile does not exist or create one when Extension is installed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
When running the following command you get no results by default:
$psEditor.Workspace.OpenFile($profile)
$profile outputs this
PS C:\Program Files (x86)\Microsoft VS Code Insiders
$profile
C:\Users\i2871rbp\Documents\WindowsPowerShell\Microsoft.VSCode_profile.ps1
However, the file does not actually exist, so when you try to have code open it, it does nothing and gives no feedback.
Can the EditorServices check for the profile and create it if it is missing upon installation? I am just thinking from an ease of use for normal powershell users who may not have a ton of Dev type experience, it might be a bad experience for them.
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 mentioned $psEditor.Workspace.OpenFile($profile) behavior and the Extension installation flow. Clarify whether a missing profile should be created, reported, or handled by both paths; done means users receive feedback or get a usable profile when it does not exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100