PowerShell / PowerShell/PowerShellEditorServices
Add ability to New WIndow with Folder or Open Folder in Current Window
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
When working with Editor Commands, it would be nice to be able to Open a new instance of Code with a specified folder as a project directory.
Example;
- Create new module with Plaster with Editor Command.
- After Plaster is finished, the Editor Command then Opens a new Code window with the Module Root as Project Folder.
I would actually prefer if it could open the folder in the current Window if Code supported multiple project folders (I'm getting tired of having 15-20 Code Windows open.)
I wouldn't also mind being able to just open the Project in the current Windows as well.
Is there any sort of way to accomplish this? So far, trying to use code command line is totally worthless if I already have a code window open. This is actually something really frustrating that makes the "Open in Code" or "Open in Code Insiders" totally worthless. I need to check the status of these sort of issues on the Code issues. Right now, I have to use Insiders for my normal Projects, and normal Code for my "Open with".
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 with the Editor Commands and code command-line behavior described in the issue, including the Plaster workflow and the distinction between a new Code window and opening a folder in the current window. Check the referenced Code and Code Insiders issue status before determining whether this belongs in PowerShell Editor Services. Done would require a clear supported path or a documented limitation for opening project folders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100