Open
Description
There are many known issues in this area and we need to address all these.
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
{{ message }}
No type
None yet
Activity
ghost commentedon Oct 29, 2020
Thanks for contacting us.
We're moving this issue to the
Next sprint planningmilestone 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 commentedon Nov 4, 2020
cc @vijayrkn on this - how much of this you would estimate is on VS and not .NET?
vijayrkn commentedon Nov 4, 2020
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 commentedon Nov 4, 2020
thanks @vijayrkn
dougbu commentedon Mar 22, 2021
@mkArtakMSFT what specific problems does this issue encompass❔
davidfowl commentedon Mar 22, 2021
I hope part of it is improving the quality of the generated code.
bradygaster commentedon Mar 22, 2021
@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.
9 remaining items
captainsafia commentedon Oct 8, 2021
@dougbu Ah, fair enough. Is there a writeup of the known issues in this space? Are they all logged on the GitHub?
dougbu commentedon Oct 8, 2021
I think the problems are mostly in @bradygaster, @mkArtakMSFT, @glennc and maybe my head. But, see
ghost commentedon Dec 28, 2021
Thanks for contacting us.
We're moving this issue to the
.NET 7 Planningmilestone 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 commentedon Oct 11, 2022
Thanks for contacting us.
We're moving this issue to the
.NET 8 Planningmilestone 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.