PowerShell / PowerShell/PowerShellEditorServices
DBG: Prompt Injection Necessary?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 767
- Forks
- 266
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 1
Description
Is this function really necessary? The prompt function already has this DBG: detection in it, and if someone has customized the prompt (as I have), it adds an extra DBG: where it is unwanted. Perhaps a toggle feature flag via the API can be made available?
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 at src/PowerShellEditorServices/Session/Host/EditorServicesPSHostUserInterface.cs#L744-L752 and compare this function with the prompt function's existing DBG: detection. Determine whether the duplicate prompt modification is still necessary and clarify whether the intended result is removal or an API feature flag; the issue is done when customized prompts no longer receive an unwanted extra DBG:.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100