PowerShell / PowerShell/PSScriptAnalyzer

Rule to enforce strongly typed variables

Open
#2,137 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue - New Rule Up-for-Grabs
Dominant language
C#
Stars
2.2k
Forks
414
Avg merge
13h 1m
Merged PRs (30d)
2

Description

Summary of the new feature

Would be nice is PSSA could add a rule that makes sure variables are strongly typed.

Should be an optional rule, disabled by default, to not break with PowerShell default behavior. But for projects where you want high code quality, readability, and the added safety that explicit types can add, it'd be nice with a lint rule to enforce it.

I'm looking into learning Python, and got inspired by tools like:

Proposed technical implementation details (optional)

  • Error or warn when no type is used, or generic types like [object], [array] and [int].
  • Require explicit data types.

What is the latest version of PSScriptAnalyzer at the point of writing

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

No files, tests, or entry points are named. Start by reviewing PSScriptAnalyzer's existing rule architecture and the linked type-checking tools, then define the supported type cases, diagnostics, configuration, and tests needed for an optional rule that is disabled by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.