PowerShell / PowerShell/vscode-powershell
Some property types (ScriptProperty and CodeProperty) don't appear in debugger's Variables view
Open
Nobody has claimed this yet.
Area-Debugging
Issue-Bug
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
This is a follow-on issue from #821 to track the lack of ScriptProperty and CodeProperty properties when looking at a PSObject in the debugger's Variables pane. These are usually pretty helpful for debugging purposes so it'd be good to add support 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
This is a follow-on to issue #821 about the debugger's Variables pane. Start by tracing how PSObject properties are surfaced there, then determine how ScriptProperty and CodeProperty are handled. Done means these property types appear when inspecting a PSObject in the Variables view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100