noGlobalShadowing: message and severity do not match runtime behavior

Open Beginner friendly
  • Is something wrong?
#87 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start with the noGlobalShadowing rule and its message, then read docs/verification/results/globals-shadowing.md (C-001) and docs/rule-priority.md. Update the wording to describe the behavior shown by the runtime verification, and reconsider the rule’s severity and preset placement against the documented guidance. Done when the message and severity or preset placement reflect that evidence.

Written by the indexing model from the issue text.

Description

needs-triage

Runtime verification (PR #85, docs/verification/results/globals-shadowing.md, C-001) shows rebinding log or util through a module parameter fails nowhere: the parameter wins inside that module and hides the global. The rule's source (upgrade skill) says it "can break logging or utility calls". Reword the message to the real hazard and reconsider the severity and preset placement under docs/rule-priority.md.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
2h 8m
Merged PRs (30d)
64

Getting set up

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 nemchik/biome-plugin-suitescript

All issues in nemchik/biome-plugin-suitescript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.