swagger-api / swagger-api/swagger-codegen
Not overwriting the previously generated files for dotnet core generation.
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
If we use the codegen to generate clients and tests in an ongoing dotnet-core project where API endpoints are constantly changing, the newly created files would overwrite the older ones. Which is not a big deal for client code but a problem for tests, as the completed tests are deleted. Is there a way or an option to prevent this? For instance not generating the tests for already written methods or clients, sort of like an incremental generation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the dotnet-core codegen path for clients and tests and how it handles existing generated files. Done would require a defined, tested way to avoid overwriting completed tests during repeated generation, with the behavior documented for users.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100