swagger-api / swagger-api/swagger-codegen
Add support for setting executable on generated files
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Our additional supporting files include gradlew, which needs to be executable.
It doesn't appear that Swagger has an option for setting the execute bit on resources/files.
That would be a nice feature, so we don't have to postprocess.
This might be a mustache limitation, but it doesn't have to be a Swagger limitation--you could do the postprocessing.
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 how supporting files such as gradlew are emitted by Swagger Codegen and whether the Mustache-based generation path preserves file permissions. Check the relevant generation tests, if present, and verify that generated gradlew is executable without postprocessing.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100