Created by: vvb
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. 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./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master,5.3.x,6.0.x -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
This PR greatly reduces the time taken for Csharp-netcore code generation. toModelName() method is invoked numerous number of times and it was accummulating to a lot of time. This PR adds memoization to CSharp and DefaultCodeGen toModelName() methods. This has reduced the C# SDK generation time for our rather large openapi spec from ~2 hours to 4 mins. This has reduced the Golang SDK generation time for our rather large openapi spec from ~1h30m hours to 4 mins.
The generated code is the same as before.