-
Notifications
You must be signed in to change notification settings - Fork 440
Added github issues templates #1952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 17 commits
e927b0c
a0a074c
89528a7
42c06eb
b5dbb51
ea7855b
9e6656b
dfb8fc9
d5303ec
1ff166c
8cdad46
ed57b88
1787248
b19b9df
3a72cfa
c1f0d49
f2e1b02
9a3b198
3d83efb
cb971b2
8cf2e37
755a79b
64c02f8
d306aa4
5ce2fe6
5170573
978f584
21644e4
86eca89
230f958
c2d5d65
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
blank_issues_enabled: true | ||
issue_templates: | ||
- name: 🔍 Typings Inconsistency | ||
description: Report inconsistencies between TypeScript's web API typings and browser behavior. | ||
labels: [lib.d.ts bug] | ||
file: typings_inconsistency.yml |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
name: "Typings Inconsistency" | ||
title: "[Typings Inconsistency] " | ||
labels: [lib.d.ts bug] | ||
assignees: [] | ||
description: "Report inconsistencies between TypeScript's web API typings and browser behavior." | ||
body: | ||
- type: markdown | ||
attributes: | ||
value: | | ||
## Typings Inconsistency | ||
Provide details of the inconsistency. | ||
- type: input | ||
id: inconsistency_summary | ||
attributes: | ||
label: "Summary" | ||
description: "Brief summary of the inconsistency" | ||
placeholder: "e.g., Mismatch in event handling..." | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: expected_vs_actual | ||
attributes: | ||
label: "Expected vs. Actual Behavior" | ||
description: "Describe what you expected and what actually happened" | ||
placeholder: "Expected: ...\nActual: ..." | ||
validations: | ||
required: true | ||
- type: textarea | ||
id: steps | ||
attributes: | ||
label: "Playground link" | ||
description: "Paste the playground link" | ||
placeholder: "https://www.typescriptlang.org/play/..." | ||
validations: | ||
required: true | ||
- type: checkboxes | ||
id: browser_support | ||
attributes: | ||
label: "Browser Support" | ||
description: "Ensure that the API is supported in at least two major browser engines (not two chromiums)." | ||
options: | ||
- label: "This API is supported in at least two major browser engines (not two chromiums)." | ||
validations: | ||
required: true | ||
- type: checkbox | ||
id: use_latest_typescript | ||
attributes: | ||
label: "Use Latest TypeScript Package" | ||
description: "Check this if you are using the latest TypeScript package." | ||
options: | ||
- label: "I am using the latest version of TS" | ||
validations: | ||
required: true | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd like to add "already tried @types/web package" and "already tried the latest TypeScript release", given people sometimes file issues based on outdated libs. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nothing mentions @types/web though? |
||
- type: textarea | ||
id: additional_context | ||
attributes: | ||
label: "Additional Context" | ||
description: "Any extra information, logs, or references" | ||
placeholder: "Optional details..." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, I forgot to submit this comment, sorry:
Type definition is what DefinitelyTyped calls it, so let's use that word. Maybe "Web API type definition issue". An issue would be more general than inconsistency which wouldn't cover type enhancements.