Variable colors are prioritized over hashtable colors for keys in hashtables

Open
#182 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
powershell
Domain
tooling

Research direction

Start by locating the hashtable grammar rules that assign the "variable.*" and "meta.hashtable.assignment" scopes. Use VS Code's Inspect TM Scopes feature on a hashtable key to compare the current scope precedence. Done means hashtable keys receive the specific hashtable scope so they can be colored independently from variables.

Written by the indexing model from the issue text.

Description

Keys inside hashtables use the "variable.*" scope over the more specific "meta.hashtable.assignment" scope, this means you can't give keys inside hashtables a custom color that is different from variables.

HashtableKeyProblem

(Screenshot is from VS code using the "Inspect TM scopes" feature)

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.