You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- use more modern C# syntax
- remove extra `AssemblyTestLog.Create(...)` overload
- was just used in tests and other overload already more direct (and worth testing)
- remove useless `ILoggedTest` interface
- add solution filter and startvs.cmd file
- make `LoggedTestBase` an `abstract` class
- remove unused `using`s
- shorten long Lines
- also clean 30_api_proposal.md line endings
We welcome API proposals! We have a process to evaluate the value and shape of new API. There is an overview of our process [here](https://github.com/dotnet/aspnetcore/blob/main/docs/APIReviewProcess.md). This template will help us gather the information we need to start the review process.
14
-
First, please describe the purpose and value of the new API here.
15
-
-->
16
-
17
-
## Proposed API
18
-
19
-
<!--
20
-
Please provide the specific public API signature diff that you are proposing. For example:
21
-
```diff
22
-
namespace Microsoft.AspNetCore.Http
23
-
{
24
-
public static class HttpResponseWritingExtensions
25
-
{
26
-
+ public Task WriteAsync(this HttpResponse response, StringBuilder builder);
27
-
}
28
-
}
29
-
```
30
-
You may find the [Framework Design Guidelines](https://github.com/dotnet/runtime/blob/master/docs/coding-guidelines/framework-design-guidelines-digest.md) helpful.
31
-
-->
32
-
33
-
## Usage Examples
34
-
35
-
<!--
36
-
Please provide code examples that highlight how the proposed API additions are meant to be consumed.
37
-
This will help suggest whether the API has the right shape to be functional, performant and useable.
38
-
You can use code blocks like this:
39
-
``` C#
40
-
// some lines of code here
41
-
```
42
-
-->
43
-
44
-
## Alternative Designs
45
-
46
-
<!--
47
-
Were there other options you considered, such as alternative API shapes?
48
-
How does this compare to analogous APIs in other ecosystems and libraries?
49
-
-->
50
-
51
-
## Risks
52
-
53
-
<!--
54
-
Please mention any risks that to your knowledge the API proposal might entail, such as breaking changes, performance regressions, etc.
55
-
-->
56
-
1
+
---
2
+
name: API proposal
3
+
about: Propose a change to the public API surface
4
+
title: ''
5
+
labels: api-suggestion
6
+
assignees: ''
7
+
8
+
---
9
+
10
+
## Background and Motivation
11
+
12
+
<!--
13
+
We welcome API proposals! We have a process to evaluate the value and shape of new API. There is an overview of our process [here](https://github.com/dotnet/aspnetcore/blob/main/docs/APIReviewProcess.md). This template will help us gather the information we need to start the review process.
14
+
First, please describe the purpose and value of the new API here.
15
+
-->
16
+
17
+
## Proposed API
18
+
19
+
<!--
20
+
Please provide the specific public API signature diff that you are proposing. For example:
21
+
```diff
22
+
namespace Microsoft.AspNetCore.Http
23
+
{
24
+
public static class HttpResponseWritingExtensions
25
+
{
26
+
+ public Task WriteAsync(this HttpResponse response, StringBuilder builder);
27
+
}
28
+
}
29
+
```
30
+
You may find the [Framework Design Guidelines](https://github.com/dotnet/runtime/blob/master/docs/coding-guidelines/framework-design-guidelines-digest.md) helpful.
31
+
-->
32
+
33
+
## Usage Examples
34
+
35
+
<!--
36
+
Please provide code examples that highlight how the proposed API additions are meant to be consumed.
37
+
This will help suggest whether the API has the right shape to be functional, performant and useable.
38
+
You can use code blocks like this:
39
+
``` C#
40
+
// some lines of code here
41
+
```
42
+
-->
43
+
44
+
## Alternative Designs
45
+
46
+
<!--
47
+
Were there other options you considered, such as alternative API shapes?
48
+
How does this compare to analogous APIs in other ecosystems and libraries?
49
+
-->
50
+
51
+
## Risks
52
+
53
+
<!--
54
+
Please mention any risks that to your knowledge the API proposal might entail, such as breaking changes, performance regressions, etc.
0 commit comments