You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.yml
+23-23
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,19 @@
1
-
name: "Feature request"
2
-
description: "Suggest an idea"
1
+
name: 'Feature request'
2
+
description: 'Suggest an idea'
3
3
body:
4
4
- type: markdown
5
5
attributes:
6
-
value: "Please fill in each section completely. Thank you!"
6
+
value: 'Please fill in each section completely. Thank you!'
7
7
- type: textarea
8
8
id: search_terms
9
9
attributes:
10
-
label: "🔍 Search Terms"
10
+
label: '🔍 Search Terms'
11
11
description: |
12
-
💡 Did you know? TypeScript has over 2,000 open suggestions!
12
+
💡 Did you know? TypeScript has over 2,000 open suggestions!
13
13
14
-
🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
14
+
🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
15
15
16
-
The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests
16
+
The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests
17
17
placeholder: |
18
18
List of keywords you searched for before creating this issue.
19
19
Write them down here so that others can find this suggestion more easily and help provide feedback.
@@ -24,44 +24,44 @@ body:
24
24
- type: checkboxes
25
25
id: viability_checklist
26
26
attributes:
27
-
label: "✅ Viability Checklist"
27
+
label: '✅ Viability Checklist'
28
28
description: |
29
29
Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
30
30
We always recommend reviewing the TypeScript design goals before investing time writing
31
31
a proposal for ideas outside the scope of the project.
32
32
33
33
My suggestion meets the following guidelines.
34
34
options:
35
-
- label: This wouldn't be a breaking change in existing TypeScript/JavaScript code
36
-
required: true
37
-
- label: This wouldn't change the runtime behavior of existing JavaScript code
38
-
required: true
39
-
- label: This could be implemented without emitting different JS based on the types of the expressions
40
-
required: true
41
-
- label: This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
42
-
required: true
43
-
- label: "This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals"
44
-
required: true
35
+
- label: This wouldn't be a breaking change in existing TypeScript/JavaScript code
36
+
required: true
37
+
- label: This wouldn't change the runtime behavior of existing JavaScript code
38
+
required: true
39
+
- label: This could be implemented without emitting different JS based on the types of the expressions
40
+
required: true
41
+
- label: This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
42
+
required: true
43
+
- label: 'This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals'
44
+
required: true
45
45
- type: textarea
46
46
id: suggestion_summary
47
47
attributes:
48
-
label: "⭐ Suggestion"
48
+
label: '⭐ Suggestion'
49
49
description: "A summary of what you'd like to see added or changed"
50
50
validations:
51
51
required: true
52
52
- type: textarea
53
53
id: motivating_example
54
54
attributes:
55
-
label: "📃 Motivating Example"
55
+
label: '📃 Motivating Example'
56
56
description: |
57
-
If you were announcing this feature in a blog post, what's a short
58
-
explanation that shows a developer why this feature improves the language?
57
+
If you were announcing this feature in a blog post, what's a short
58
+
explanation that shows a developer why this feature improves the language?
59
59
validations:
60
60
required: true
61
61
- type: textarea
62
62
id: use_cases
63
63
attributes:
64
-
label: "💻 Use Cases"
64
+
label: '💻 Use Cases'
65
65
value: |
66
66
1. What do you want to use this for?
67
67
2. What shortcomings exist with current approaches?
description: "Fix or improve issues with built-in type definitions like `lib.dom.d.ts`, `lib.es6.d.ts`, etc."
1
+
name: 'Library change'
2
+
description: 'Fix or improve issues with built-in type definitions like `lib.dom.d.ts`, `lib.es6.d.ts`, etc.'
3
3
body:
4
4
- type: markdown
5
5
attributes:
@@ -18,45 +18,45 @@ body:
18
18
- type: markdown
19
19
attributes:
20
20
value: |
21
-
If you're missing common new methods like `Array.includes`, you may have a misconfigured project.
22
-
Try setting `lib: "es2020"` and checking whether the type you want is present.
23
-
You can diagnose further by running `tsc` with `--listFilesOnly` or `--showConfig`.
21
+
If you're missing common new methods like `Array.includes`, you may have a misconfigured project.
22
+
Try setting `lib: "es2020"` and checking whether the type you want is present.
23
+
You can diagnose further by running `tsc` with `--listFilesOnly` or `--showConfig`.
24
24
25
-
Conversely, if you are seeing built-in methods you expect to *not* see, check your 'lib' setting or review your dependencies for lib/reference directives that might be polluting
26
-
your global scope. This is common when using the 'node' type library. See https://github.com/microsoft/TypeScript/issues/40184
25
+
Conversely, if you are seeing built-in methods you expect to *not* see, check your 'lib' setting or review your dependencies for lib/reference directives that might be polluting
26
+
your global scope. This is common when using the 'node' type library. See https://github.com/microsoft/TypeScript/issues/40184
27
27
- type: input
28
28
id: compilation_target
29
29
attributes:
30
-
label: "⚙ Compilation target"
30
+
label: '⚙ Compilation target'
31
31
description: "What's your compilation target (e.g.: `ES2015`)?"
32
32
validations:
33
33
required: true
34
34
- type: input
35
35
id: current_lib
36
36
attributes:
37
-
label: "⚙ Library"
37
+
label: '⚙ Library'
38
38
description: "What's the current library you're using?"
39
39
validations:
40
40
required: true
41
41
- type: textarea
42
42
id: incorrect_definition
43
43
attributes:
44
-
label: "Missing / Incorrect Definition"
45
-
description: "What property, method, function, etc. is missing or incorrect?"
44
+
label: 'Missing / Incorrect Definition'
45
+
description: 'What property, method, function, etc. is missing or incorrect?'
46
46
validations:
47
47
required: true
48
48
- type: textarea
49
49
id: sample_code
50
50
attributes:
51
-
label: "Sample Code"
51
+
label: 'Sample Code'
52
52
description: "What's some code using this that should work, but doesn't?"
53
53
render: TypeScript
54
54
validations:
55
55
required: true
56
56
- type: textarea
57
57
id: documentation_link
58
58
attributes:
59
-
label: "Documentation Link"
59
+
label: 'Documentation Link'
60
60
description: |
61
61
Link to relevant documentation (e.g. MDN, W3C, ECMAScript Spec) to consult for this property.
62
62
Note that lib.dom.d.ts intentionally does not include browser-specific extensions or early experimental features.
0 commit comments