Syntax Highlighting Only Helps differentiate between

Open
#163 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
powershell
Domain
tooling

Research direction

Start by locating the PowerShell syntax-highlighting definitions in the EditorSyntax repository and reproduce the provided code sample in the listed editors and themes. Compare highlighting for commands, variables, parameters, methods, properties, and $_; done means these categories receive consistent, distinct colors where the grammar supports them.

Written by the indexing model from the issue text.

Description

Environment
  • Editor and Version (VS Code, Atom, Sublime (tried in all 3 problem has been there for a year if not more)):
  • Your primary theme: Monokai
Issue Description
  • Syntactical components are not as distinguished by color as they should be.
  • Variables, Parameters/Switches, methods/properties all share the same color
  • Commands/Functions can be different colors after a pipe
  • Commands/Functions, Variables, Parameters/Switches, methods/properties should each have their own individual color
  • There seems to be another problem of inconsistency in color with $_ and $_.
  • Monokai was just one of the better ones, it was worse in most other themes, including the vscode default dark, and powershell ISE theme
Screenshots

image

Expected Behavior
  • Commands/Functions, Variables, Parameters/Switches, methods/properties should each have their own individual color REGARDLESS of theme
Code Samples

$variable  = (Select-Object -Property Item, "Item2").item[0] 
$variable.method | Where ($_.something -eq "$word")
$date = Get-Date
$date.day
Dominant language
PowerShell
Stars
151
Forks
55
No merged PRs in 30d

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/EditorSyntax

All issues in PowerShell/EditorSyntax

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.