1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
name: "Feature request"
description: "Suggest an idea"
body:
- type: markdown
attributes:
value: "Please fill in each section completely. Thank you!"
- type: textarea
id: search_terms
attributes:
label: "🔍 Search Terms"
description: |
💡 Did you know? TypeScript has over 2,000 open suggestions!
🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests
placeholder: |
List of keywords you searched for before creating this issue.
Write them down here so that others can find this suggestion more easily and help provide feedback.
validations:
required: true
- type: checkboxes
id: viability_checklist
attributes:
label: "✅ Viability Checklist"
description: |
Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
We always recommend reviewing the TypeScript design goals before investing time writing
a proposal for ideas outside the scope of the project.
My suggestion meets the following guidelines.
options:
- label: This wouldn't be a breaking change in existing TypeScript/JavaScript code
required: true
- label: This wouldn't change the runtime behavior of existing JavaScript code
required: true
- label: This could be implemented without emitting different JS based on the types of the expressions
required: true
- label: This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
required: true
- label: "This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals"
required: true
- type: textarea
id: suggestion_summary
attributes:
label: "⭐ Suggestion"
description: "A summary of what you'd like to see added or changed"
validations:
required: true
- type: textarea
id: motivating_example
attributes:
label: "📃 Motivating Example"
description: |
If you were announcing this feature in a blog post, what's a short
explanation that shows a developer why this feature improves the language?
validations:
required: true
- type: textarea
id: use_cases
attributes:
label: "💻 Use Cases"
value: |
1. What do you want to use this for?
2. What shortcomings exist with current approaches?
3. What workarounds are you using in the meantime?
validations:
required: true
|
