Use InferFromServicesAttribute to infer non-interface parameters in minimal actions come from services

[halter73]

builder.Services.AddDbContext<ApplicationDbContext>(
// ...

app.MapPost("/todos", (ApplicationDbContext context) => { 
// ...

Today, the above call to MapPost would attempt to deserialize the ApplicationDbContext from a JSON body because there's no attribute and ApplicationDbContext is a non-interface, non-TryParsable type. Adding [FromServices] to the parameter fixes the issue, but it would be nice if for certain non-interface, non-TryParsable types like types derived from DbContext were inferred to come from services by default.

One way we could do this is by looking at each parameter type and checking if that type or any of its parents have a certain attribute. Maybe we could call it InferFromServicesAttribute. Because we want libraries like EF to use this without needing to take a dependency on ASP.NET Core packages, we probably want to look for this attribute by name.

@ajcvickers

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[davidfowl]

We're no longer doing this. Replaced by #32737 instead.