Modify "feature request" template for more natural user experience #1964
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
saulfield
approved these changes
Apr 17, 2023
Gamenot
reviewed
Apr 17, 2023
Adaickalavan
approved these changes
Apr 18, 2023
|
@qianyi-sun Please merge this when you have the chance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The structure of current "feature request" issue template is "Proposal" then "Motivation", which is easier for us to read as devs because when we check it we can always see the solution that user would like first.
But from user's perspective, it might be more logically natural for general writing if motivation/context goes first, and followed by the possible solution.
Still not sure if we should do this since either way has its pros/cons, sall comments are welcomed!