Merge master into feature/GraphingCalculator branch (#585)
* Merge master into feature/GraphingCalculator branch
This commit is contained in:
13
.github/ISSUE_TEMPLATE/feature_request.md
vendored
13
.github/ISSUE_TEMPLATE/feature_request.md
vendored
@@ -13,7 +13,7 @@ See https://github.com/Microsoft/calculator/blob/master/docs/NewFeatureProcess.m
|
||||
|
||||
**Problem Statement**
|
||||
<!--
|
||||
What problem are we trying to solve? Who’s the target audience? Is there a customer need or pain point we need to remedy? Is there a business goal or metric we are trying to improve? Do we have a hypothesis we want to prove or disprove?
|
||||
What problem are we trying to solve? Who’s the target audience? Is there a customer need or pain point we need to remedy? Is there a business goal or metric we are trying to improve? Do we have a hypothesis we want to prove or disprove?
|
||||
-->
|
||||
|
||||
**Evidence or User Insights**
|
||||
@@ -41,3 +41,14 @@ Things we are explicitly not doing or supporting or that are out of scope, inclu
|
||||
<!--
|
||||
Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage.
|
||||
-->
|
||||
|
||||
**Requested Assignment**
|
||||
<!--
|
||||
Some people just want to suggest a feature and let someone else implement it.
|
||||
Other people want to not only suggest a feature, but implement it as well.
|
||||
Both scenarios are completely ok. We just want to know which one it is.
|
||||
We are likely to prioritize the review of feature requests if they already have someone who can implement them.
|
||||
Please indicate which bucket you fall into by keeping one and removing the other.
|
||||
-->
|
||||
If possible, I would like to implement this.
|
||||
I'm just suggesting this idea. I don't want to implement it.
|
||||
|
||||
Reference in New Issue
Block a user