Microsoft.dotnet-openapi should generate files in the project hive

[ddobric]

When using Microsoft.dotnet-openapi tool, files are generated in the /obj folder.
In some projects, we are required to extend generated files by using partial or extension methods.
To make this possible, it would be helpful to generate files inside the project hive.

[pranavkm]

@ddobric it shouldn't really matter where the code is generated. The compiler will work fine as long as the generated types are partial. Is there a specific scenario that is blocked?

[ddobric]

It is more about how to deal with generates code. It is not fist time that we make usage of generated code. We had and have that for long time. For example WCF.
Expectation so following:

1. Devs generate code with out of VS and do whatever they think it is right .
2. Devs use VS to generate code. On this case dev1 generates code in obj folder. In the meantime service was changed and dev one opens the solution. I guess, VS will generate code against new service version, which might not be right one.
   It would be helpful to generate code in as the part of the solution, so we can commit it to the repo. In that case regeneration of the code should happen explicitly on demand.
   Some projects required that and some don't. It should be good to support both approaches.

Thanks

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.