microsoft / microsoft/TypeScript
Allow protected/private index signatures
Open
Nobody has claimed this yet.
Awaiting More Feedback
Needs Proposal
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
TS1071 private protected index number string signature
Suggestion
I can't dope out why it's not supported
Use Cases
Examples
class List {
private [index :number] :Task
public * [Symbol.iterator] () :Generator<Task> {}
}
Checklist
My suggestion meets these guidelines:
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the TS1071 search term and the class List example in this issue to understand the requested private index signature. Investigate where TypeScript validates index signatures and how protected/private visibility is represented. Done means the example is accepted without changing emitted JavaScript, with behavior consistent with TypeScript's design goals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100