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/bug_report.yml
+8-10
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,7 @@ body:
13
13
14
14
List them here so people in the future can find this one more easily.
15
15
placeholder: |
16
-
List of keywords you searched for before creating this issue.
17
-
Write them down here so that others can find this bug more easily and help provide feedback.
16
+
List of keywords you searched for before creating this issue. Write them down here so that others can find this bug more easily and help provide feedback.
18
17
19
18
e.g. "function inference any", "jsx attribute spread", "move to file duplicate imports", "discriminated union inference", "ts2822"
20
19
validations:
@@ -26,21 +25,19 @@ body:
26
25
description: |
27
26
When did you start seeing this bug occur?
28
27
29
-
"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
"Bugs" that have existed in TS for a long time are very likely to be FAQs; please refer to the [FAQ wiki page](https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs).
31
29
30
+
Please try the nightly version of TS to see if it's already been fixed. Install `typescript@next` or use the [Playground](http://www.typescriptlang.org/play/?ts=Nightly).
32
31
33
-
If possible, please try testing the nightly version of TS to see if it's already been fixed. For npm: `typescript@next`
32
+
If possible, try bisecting the issue using [every-ts](https://www.npmjs.com/package/every-ts#bisecting), which should narrow down the problem to a specific change.
34
33
35
-
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
36
-
37
-
38
-
Note: The TypeScript Playground can be used to try older versions of TypeScript.
34
+
The Playground also supports versions of TypeScript back to TypeScript 3.3.
39
35
40
36
Please keep and fill in the line that best applies.
41
37
value: |
42
38
- This is a crash
43
39
- This changed between versions ______ and _______
40
+
- This changed in commit or PR _______
44
41
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
45
42
- I was unable to test this on prior versions because _______
46
43
validations:
@@ -54,7 +51,6 @@ body:
54
51
55
52
This should have the same code as the code snippet below, and use whichever settings are relevant to your report.
56
53
57
-
58
54
As a last resort, you can link to a repo, but these will be slower for us to investigate.
59
55
placeholder: 'Playground link with relevant code: https://www.typescriptlang.org/play?#code/PTAEFkE9QYwewCYFNQHM5IM6gBZIE5JA'
60
56
validations:
@@ -65,6 +61,7 @@ body:
65
61
label: 💻 Code
66
62
description: |
67
63
Please post the relevant code sample here as well.
64
+
68
65
This code and the Playground code should be the same, do not use separate examples.
69
66
70
67
We can quickly address your report if:
@@ -74,6 +71,7 @@ body:
74
71
- The incorrectness of the behavior is readily apparent from reading the sample.
75
72
76
73
Reports are slower to investigate if:
74
+
77
75
- We have to pare too much extraneous code.
78
76
- We have to clone a large repo and validate that the problem isn't elsewhere.
79
77
- The sample is confusing or doesn't clearly demonstrate what's wrong.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.yml
+5-7
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,7 @@ body:
15
15
16
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
-
List of keywords you searched for before creating this issue.
19
-
Write them down here so that others can find this suggestion more easily and help provide feedback.
18
+
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.
20
19
21
20
e.g. "isArray readonly", "regex string types", "json const assertion import"
22
21
validations:
@@ -26,9 +25,7 @@ body:
26
25
attributes:
27
26
label: '✅ Viability Checklist'
28
27
description: |
29
-
Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
30
-
We always recommend reviewing the TypeScript design goals before investing time writing
31
-
a proposal for ideas outside the scope of the project.
28
+
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.
32
29
33
30
My suggestion meets the following guidelines.
34
31
options:
@@ -40,6 +37,8 @@ body:
40
37
required: true
41
38
- label: This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
42
39
required: true
40
+
- label: "This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types"
41
+
required: true
43
42
- label: 'This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals'
44
43
required: true
45
44
- type: textarea
@@ -54,8 +53,7 @@ body:
54
53
attributes:
55
54
label: '📃 Motivating Example'
56
55
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?
56
+
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?
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/lib_change.yml
+5-11
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
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.'
2
+
description: 'Fix or improve issues with built-in type definitions like `lib.es6.d.ts`, etc.'
3
3
body:
4
4
- type: markdown
5
5
attributes:
@@ -12,18 +12,13 @@ body:
12
12
* Array methods - see https://github.com/microsoft/TypeScript/issues/36554
13
13
* `parseInt`, `parseFloat`, `isFinite`, `isNaN`, etc. - see https://github.com/microsoft/TypeScript/issues/4002
14
14
15
-
16
-
The DOM lib is maintained elsewhere and you can skip a step by filing issues/PRs for the DOM at that repo.
17
-
See https://github.com/microsoft/TypeScript-DOM-lib-generator
15
+
The DOM lib is maintained elsewhere and you can skip a step by filing issues/PRs for the DOM at that repo. See https://github.com/microsoft/TypeScript-DOM-lib-generator
18
16
- type: markdown
19
17
attributes:
20
18
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`.
19
+
If you're missing common new methods like `Array.includes`, you may have a misconfigured project. Try setting `lib: "es2020"` and checking whether the type you want is present. You can diagnose further by running `tsc` with `--listFilesOnly` or `--showConfig`.
24
20
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
21
+
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 your global scope. This is common when using the 'node' type library. See https://github.com/microsoft/TypeScript/issues/40184
27
22
- type: input
28
23
id: compilation_target
29
24
attributes:
@@ -58,5 +53,4 @@ body:
58
53
attributes:
59
54
label: 'Documentation Link'
60
55
description: |
61
-
Link to relevant documentation (e.g. MDN, W3C, ECMAScript Spec) to consult for this property.
62
-
Note that lib.dom.d.ts intentionally does not include browser-specific extensions or early experimental features.
56
+
Link to relevant documentation (e.g. MDN, W3C, ECMAScript Spec) to consult for this property. Note that lib.dom.d.ts intentionally does not include browser-specific extensions or early experimental features.
0 commit comments