Polymer pass: Warn when there is a mismatch between the type in the code and the @type

Repository metrics

Stars

7,176 stars (7,176 stars)

PR merge metrics

Avg merge 12d 15h (Avg merge 12d 15h)1 merged PR in 30d (1 merged PR in 30d)

Description

Polymer({
    ...
    /**
     * @type {string}
     */
    someField: Number,
});

Contributor guide

Research direction

Start by examining the existing Polymer pass implementation (likely PolymerPass.java) in the Closure Compiler source. Understand how @type annotations are processed and how type mismatch warnings are currently emitted for non Polymer code. The issue requires adding a new warning for Polymer specific type mismatches. Check the comments on this issue for any additional context from the assignee. Look at how similar warnings are implemented in other pass files for patterns.

Tech stack

javascript

Domain

tooling

Issue type

Feature

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.

3-5 days

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

JavaClosure Compiler internalsPolymerJSDoc

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

25