Use `Jinja2` + static template files to replace our existing static binding generator template engines.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 62
- Forks
- 28
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 5
Description
We use f-template and string replacement for the code gen process, which brings in a lot of difficulty in reviewing and implementing new features. Developers needs to explicitly track the indentations. Writing a jinja2 template can alleviate from handling the indentation inline. In addition, it provides features like loops and conditionals which I expect should greatly reduce the complexity in codegen.
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 locating the code-generation process that uses f-template and string replacement, then inventory the existing template engines and generated outputs. Evaluate how static Jinja2 templates would cover the current generation paths, including loops and conditionals. Done means the existing binding generation behavior is migrated without the inline indentation handling described in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100