* 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>
60 lines
2 KiB
Markdown
60 lines
2 KiB
Markdown
---
|
|
name: Feature Request
|
|
about: Suggest an idea
|
|
title: ''
|
|
labels: ''
|
|
assignees: ''
|
|
---
|
|
# Suggestion
|
|
|
|
<!--
|
|
Please fill in each section completely. Thank you!
|
|
-->
|
|
|
|
## 🔍 Search Terms
|
|
|
|
<!--
|
|
💡 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
|
|
|
|
Replace the text below:
|
|
-->
|
|
|
|
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
|
|
|
|
<!--
|
|
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 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](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
|
|
|
|
|
|
## ⭐ Suggestion
|
|
|
|
<!-- A summary of what you'd like to see added or changed -->
|
|
|
|
## 📃 Motivating Example
|
|
|
|
<!--
|
|
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?
|
|
-->
|
|
|
|
## 💻 Use Cases
|
|
|
|
<!--
|
|
What do you want to use this for?
|
|
What shortcomings exist with current approaches?
|
|
What workarounds are you using in the meantime?
|
|
-->
|