[aspnetcore] Added parameter to generate models in a seperate csproj#13024
[aspnetcore] Added parameter to generate models in a seperate csproj#13024wing328 merged 3 commits intoOpenAPITools:masterfrom
Conversation
|
@knom thanks for the PR. Can you please elaborate on the use case for this option? cc @mandrean (2017/08) @frankyjuang (2019/09) @shibayan (2020/02) @Blackclaws (2021/03) @lucamazzanti (2021/05) |
| { | ||
| supportingFiles.add(new SupportingFile("ModelsProject.csproj.mustache", sourceFolder + File.separator + modelPackage, modelPackage + ".csproj")); | ||
| } | ||
|
|
There was a problem hiding this comment.
can you please update the Java code to conform the java code style? e.g.
if (...) {
// do something
} else {
// do something else
}There was a problem hiding this comment.
Fine @wing328 I've refactored the IF/ELSEs
In C# some folks like to have MODELS in a seperate C# project from the CONTROLLERS and stuff. The new switch will generate 2 projects:
|
|
Thanks for the explanation. Let's give it a try. |
|
I guess we'd probably need special sample generators and CI test.. I tried to do that in #13044. |
@wing328
[aspnetcore] Added parameter to generate models in a seperate csproj
Now a seperate CSPROJ can be generated for MODELS.
PR checklist
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.For Windows users, please run the script in Git BASH.
master(6.1.0) (minor release - breaking changes with fallbacks),7.0.x(breaking changes without fallbacks)