stenciljs/eslint-plugin

props-must-be-readonly rule

Open

#3 opened on Sep 26, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)TypeScript (37 forks)auto 404
Help Wantedtriage

Repository metrics

Stars
 (71 stars)
PR merge metrics
 (PR metrics pending)

Description

props-must-be-readonly rule is not a good idea because it will make a wrong generated components.d.ts https://github.com/ionic-team/stencil/issues/1896

Contributor guide

Research direction
Examine the rule implementation and the linked Stencil issue to understand the conflict between enforcing readonly props and generating correct type definitions.
Tech stack
typescript
Domain
frontendtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
TypeScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70