`namespaces` rule doesn't respect scopes

Repository metrics

Stars

5,940 stars (5,940 stars)

PR merge metrics

Avg merge 138d 22h (Avg merge 138d 22h)3 merged PRs in 30d (3 merged PRs in 30d)

Description

import React from 'react'
import * as wizards from './wizards'

// `wizards` redefined in local scope
function ComponentX({ wizards, submitWizard }) {
  return (
    <div>
      { shouldShowWizard && !isEmpty(wizards)
        // unable to validate computed reference report here at `wizards[0]`
        ? <WizardZero {...wizards[0]} onSubmit={submitWizard} /> 
        : <WhateverElse />
      }
    </div>
  )
}

Contributor guide

Research direction

Reproduce the issue by setting up a test case with a namespace import (import * as mod) and then redefining the same variable name as a function parameter. Examine the rule's scope analysis to ensure that the shadowed variable does not trigger false positives. The fix likely involves checking whether the imported namespace is shadowed by a local variable.

Tech stack

javascript

Domain

tooling

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

Half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

JavaScript

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70