nushell / nushell/vscode-nushell-lang

Chained assignment should be an error/warning

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

Nobody has claimed this yet.

Dominant language
Nushell
Stars
153
Forks
31
PR merge metrics
No merged PRs in 30d

Description

At the moment, we can write

$env.foo = $env.bar = "baz"

and even

let $foo = let $bar = "baz"

without any warning, but the resulting values are

$env.foo == null
$env.bar == "baz"

which is most likely not what was expected.

I think this should be reported as a warning (or even an error if there are no actual use cases for this syntax).

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.

Research direction

Begin with the chained-assignment examples in the issue and determine whether this VS Code extension can report the Nushell behavior as a warning or error. Clarify whether the syntax has valid use cases, then define the diagnostic behavior and its completion criteria before locating the relevant extension entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.