Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add an EditorInfo field to $psEditor

Open
#679 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
powershell
Domain
developer-experience, tooling

Research direction

The issue names no files, tests, or entry points. Start by locating the existing $psEditor implementation and its public properties, then review how editor-specific information is exposed. Done means agreeing on the EditorInfo shape and exposing editor name and version without implementing ISEOptions.

Written by the indexing model from the issue text.

Description

Area-psEditor Issue-Discussion Issue-Enhancement

We should add a simple info object to $psEditor so information like editor name and version can be queried from $psEditor. Since we should theoretically support many editors, we could require a few standard fields or we could just make it an object and let editors decide what information they provide.

I'm not saying we should try to implement ISEOptions here as that would be a lot more work. Just an information field along the lines of $PSVersionTable.

Dominant language
C#
Stars
767
Forks
266
Avg merge
3d 16h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PowerShellEditorServices

All issues in PowerShell/PowerShellEditorServices

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.