OpenAPITools / OpenAPITools/openapi-generator
[Discussion] Can we do better than Mustache templates?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
I have been trying to fix some issues and I must say the Mustache templates do not help. It is so incredibly hard to get oriented in them.
Was there ever any attempt to use something more sophisticated that would allow us to reuse pieces of template logic and allow us to use some nesting for readability?
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, tests, or entry points. Start by investigating how the current Mustache templates are organized and whether earlier attempts used a more expressive templating approach. Done would require a decided direction for reusable, nested template logic rather than an open-ended discussion.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100