From 034e300653b9e0c95b0042e2df4d9dd9238b1700 Mon Sep 17 00:00:00 2001 From: Jonathan Date: Thu, 28 Apr 2022 22:35:59 +0200 Subject: [PATCH] Use file-scoped namespaces (#68295) Use modern file-scoped namespaces instead of legacy namespaces --- .github/ISSUE_TEMPLATE/02_api_proposal.yml | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/02_api_proposal.yml b/.github/ISSUE_TEMPLATE/02_api_proposal.yml index 541bcf5..32878e1 100644 --- a/.github/ISSUE_TEMPLATE/02_api_proposal.yml +++ b/.github/ISSUE_TEMPLATE/02_api_proposal.yml @@ -25,13 +25,12 @@ body: You may find the [Framework Design Guidelines](https://github.com/dotnet/runtime/blob/main/docs/coding-guidelines/framework-design-guidelines-digest.md) helpful. placeholder: API declaration (no method bodies) value: | - ```C# - namespace System.Collections.Generic + ```csharp + namespace System.Collections.Generic; + + public class MyFancyCollection : IEnumerable { - public class MyFancyCollection : IEnumerable - { - public void Fancy(T item); - } + public void Fancy(T item); } ``` validations: @@ -44,7 +43,7 @@ body: Please provide code examples that highlight how the proposed API additions are meant to be consumed. This will help suggest whether the API has the right shape to be functional, performant and usable. placeholder: API usage value: | - ```C# + ```csharp // Fancy the value var c = new MyFancyCollection(); c.Fancy(42); -- 2.7.4