Skip to content

PowerShell Editor Services Hack Week Dec 2015

Keith Hill edited this page Dec 9, 2015 · 15 revisions

See the original announcement on PowerShell.org

On Sunday, December 6th at 11AM-12PM PST (7-8PM GMT) I’ll host a Crowdcast event to give an overview of PowerShell Editor Services, the PowerShell extension for VS Code, and other general ideas for contributions that people can make.  Participants can join to ask questions and discuss potential ideas so that we can get the ball rolling.

Join the conversation in the #editors channel of the PowerShell Slack Community

Ways to Contribute

Improve PowerShell Editor Services

  • Write and review documentation for the .NET and JSON APIs
  • Help provide good PowerShell script examples for validating language intelligence features
  • Add language features support for files in a PowerShell module project (issue #11)
  • Add language feature support for PowerShell classes (issue #14)
  • Check out the help wanted issue label for more ideas!

Improve the PowerShell extension for Visual Studio Code

  • Create new VS Code "command" features which provide helpful functionality for PowerShell
  • File bugs for cool features you’d like to see or examples of things that don’t work well yet
  • Help improve syntax highlighting for PowerShell code (issues #26 and #52)
  • Add features or fix bugs with the help wanted issue label

Add new editor integrations for PowerShell Editor Services

Use any of these projects during the hack week and provide feedback!

Projects

Atom integration

I've forked the language-powershell extension for Atom to add the basic wiring to PowerShell Editor Services, check out that repository here:

https://github.com/daviwil/language-powershell

The goal is to get basic message protocol working well enough to manage opened files and implement go to definition support for symbols. Once that is working everything else should be easier to enable over time.

Participants

If you plan to participate, please add your name, optional Twitter details, and the list of projects you're interested in helping with. If you don't yet know what you'd like to work on, put Available to help in the Projects column!

Name Projects
David Wilson @daviwil Atom integration, Sublime Text integration, PoshTools integration, general assistance
Bryan Winstead VS Code improvements/Available to Help
Joel Bennett @Jaykul Sublime Text integration
Hemanth @sqlchow Available to help
Doug Finke @dfinke blog Available to help. Added PowerShell Online Help, working on Expand Alias and integration with PowerShell Gallery.
Keith Hill @r_keith_hill blog Working on features and bugs in the display of variables during debug in VS Code.
Adam Driscoll @adamdriscoll blog PoshTools Integration. HTTP Host Process\Web Editor, Available to help.