TypeScript/.github/ISSUE_TEMPLATE/Feature_request.md
Ryan Cavanaugh 22f452c5cd
Update issue templates (#42049)
* Update issue templates

* Update .github/ISSUE_TEMPLATE/Bug_report.md

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/lib_change.md

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/lib_change.md

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/lib_change.md

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/lib_change.md

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>

* Swap some orderings

Co-authored-by: Daniel Rosenwasser <DanielRosenwasser@users.noreply.github.com>
2020-12-22 09:04:56 -08:00

2 KiB

name about title labels assignees
Feature Request Suggest an idea

Suggestion

🔍 Search Terms

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.

Viability 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, new syntax sugar for JS, etc.)
  • This feature would agree with the rest of TypeScript's Design Goals.

Suggestion

📃 Motivating Example

💻 Use Cases