PowerShell / PowerShell/DSC

Some static-analysis support

Open
#403 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Enhancement
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Summary of the new feature / enhancement

Instead of hitting a run-time error, it would be useful to have some static analysis be performed. I do wonder if it should be part of whatIf or separate since whatIf will already handle some of it:

  • schema validation of properties
  • dependsOn circular loops (although this is caught early on during execution)
  • [reference()] w/o explicit dependsOn
  • [resourceId()] that doesn't exist (think typo)
  • invalid functions or function arguments
Proposed technical implementation details (optional)

No response

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

Start by reading the existing whatIf behavior, since the issue questions whether static analysis belongs there or in a separate feature. Identify how schema validation, dependency checks, references, resource IDs, and function arguments are currently handled. The issue does not name files or tests, and completion criteria would need to be defined for the proposed checks.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
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.