scoping of operators is limited immediately following variable name

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file or test is named. Reproduce the scoping behavior with the PowerShell samples in a TextMate-compatible editor, then locate the syntax grammar rules for operators following variables. Done means valid operators such as -split receive the expected operator scope immediately after both $variable and ${variable}.

Written by the indexing model from the issue text.

Description

  • Editor and Version: VS Code: 1.26.1
  • Your primary theme: Monokai Dimmed
Issue Description

Operators scoped immediately after a variable, without whitespace, are limited to just arithmetic "[+%*/-]?=|[+/*%-] and 'other' &|(?<!\w)\.(?= )|`|,|\|, but all operators are valid (from what I can tell). This happens due to all the other operators requiring a negative look behind of a word character. The ${} variable reference correctly scopes the immediate following of the operators, because the } doesn't match the \w.

BTW, is that valid regex in the 'other' to have (?= ) or should it have been (?=\s) ??

Expected Behavior

All operators should be valid after a variable has scoped, from what I can determine.

I'm not sure this will be fixed easily due to the limited possibilities of TextMate.

Code Samples
$variable-split "3" #but this is valid operator function
${variable}-split "3" #but this is valid operator function
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.