swagger-api / swagger-api/swagger-codegen
[nodejs] Server has no CORS support
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
The generated server of type 'nodejs' does not support CORS. I think in most use-cases CORS support is desireable, so the generated server code should support CORS out-of-the-box.
What do you think?
Swagger-codegen version
2.4.0
Suggest a fix/enhancement
I'm happy to help with a PR if this enhancement is found worthwile.
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
The issue names no files or tests. Start by locating the Node.js generated-server templates and any tests covering generated server behavior, then determine how middleware and dependencies are represented. Done means a generated Node.js server supports CORS out of the box, with tests covering the resulting behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100