Microsoft/TypeScript

Leak of `noImplicitAny` checking with private static property

Open

#6,415 opened on Jan 9, 2016

View on GitHub
 (10 comments) (0 reactions) (0 assignees)TypeScript (48,455 stars) (6,726 forks)batch import
BugDomain: check: Type InferenceHelp Wanted

Description

declare class C {
  private static implicitAnyTypeProperty;
  static inherited: typeof C.implicitAnyTypeProperty;
  inherited: typeof C.implicitAnyTypeProperty;
}

expected:

$ node_modules/.bin/tsc index --noImplicitAny
index.ts(2,3): error TS7008: Member 'implicitAnyTypeProperty' implicitly has an 'any' type.

actual:

$ node_modules/.bin/tsc index --noImplicitAny

Contributor guide

Tech stack
typescript
Domain
developer experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScript compiler codebaseUnderstanding of property type inferencenoImplicitAny flag behavior
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the TypeScript checker's handling of private static properties in the context of noImplicitAny. The issue likely lies in the checker's logic for determining implicit any types for class members, specifically private static properties. Review diagnostic reporting for property declarations in `src/compiler/checker.ts`. Check for any recent changes that might have affected this behavior.