Fix client code generation experience

[mkArtakMSFT]

There are many known issues in this area and we need to address all these.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[bradygaster]

cc @vijayrkn on this - how much of this you would estimate is on VS and not .NET?

[vijayrkn]

I believe this item is only tracking the changed to the code generator itself. I am not expecting any major changes on the VS level. If there are issues that we identify, then we can create bugs for them.

[bradygaster]

thanks @vijayrkn

[dougbu]

@mkArtakMSFT what specific problems does this issue encompass❔

[davidfowl]

I hope part of it is improving the quality of the generated code.

[bradygaster]

@davidfowl i've talked with Claire and some other folks about adding a new generator that sits atop Refit. I think that'd be pretty hot.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[dougbu]

/fyi @bradygaster @mkArtakMSFT I moved this to our Backlog and removed my assignment

[bradygaster]

cc @captainsafia

[captainsafia]

@bradygaster I think we should close this in favor of #36636 which we are already tracking in the OpenAPI in .NET 7 epic.

[dougbu]

Huh @captainsafia, I'd say #36636 is much more specific and doesn't cover some issues we've observed e.g. getting @(OpenApiProjectReference) working reliably

[captainsafia]

@dougbu Ah, fair enough. Is there a writeup of the known issues in this space? Are they all logged on the GitHub?

[dougbu]

Ah, fair enough. Is there a writeup of the known issues in this space?

I think the problems are mostly in @bradygaster, @mkArtakMSFT, @glennc and maybe my head. But, see

• https://github.com/dotnet/aspnetcore/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-openapi
• aspnet/Tooling-ManualTests#390
• Add documentation to support code generator MSBuild AspNetCore.Docs#8461
• Describe new client code generation Swagger features AspNetCore.Docs#8462
• Add documentation for API description providers in web sites AspNetCore.Docs#8465

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 7 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.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 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.