From 74bc7595a8e5b40204aa30bfd5df342ad52c85b2 Mon Sep 17 00:00:00 2001 From: Lamparter Date: Sun, 21 Jul 2024 10:52:36 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=A7=91=E2=80=8D=F0=9F=92=BB=20Update=20re?= =?UTF-8?q?quested=20changes=20description?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: 0x5bfa <62196528+0x5bfa@users.noreply.github.com> Co-authored-by: 0x5BFA <62196528+0x5bfa@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/feature_request.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index 0408f0a19..abc764c05 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -19,7 +19,7 @@ body: id: required-changes attributes: label: ⚡ Required changes - description: Include a list of all API changes in the code, i.e. additions, subtractions as would be required by your proposal. These APIs should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code of usage of your new API. + description: Include a list of all required changes in the code, i.e. additions, subtractions as would be required by your proposal. These changes should be considered placeholders, so the naming is not as important as getting the concepts correct. If possible you should include some example (pseudo-)code illustrates your proposal. placeholder: | ```csharp var button = new Button ();