swagger-api / swagger-api/swagger-codegen
[JAVASCRIPT] NodeJS Code Generation. Unclear procedure to add logic to the appilcation
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
First I don't know where to ask, I hope I'm somewhat at the right place.
I generated code for a NodeJS application.
It seems taht the next step is to fill the Service files with logic. But isn't it a bad practise if I touch the generated code? From GRPC I know that you don't have to touch the generated code ever and you just use the generated classes etc.
Am I missing something here?
Swagger-codegen version
3.0.24
Steps to reproduce
Selecting Export -> Server Stub > NodeJS
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 reviewing the generated NodeJS application's Service files and the Export → Server Stub → NodeJS path described in the issue. Done means documenting whether those files are intended to be edited and explaining the supported procedure for adding application logic without relying on assumptions about generated code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- api, backend
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100