Feature request: README should have example passing variables
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- documentation
Research direction
Start in the README and inspect the existing template-renderer usage documented there. Check the C++ API to determine how variables are passed and which of std::map, third-party JSON types, QString, and QVariant/QVariantMap are supported. Add a clear example and document the supported options or extension path; done means a reader can follow the example to bind C++ values.
Written by the indexing model from the issue text.
Description
There's lot's of attention to filters, control statements, etc, but no example how do you bind (pass) C++ values into template renderer.
Does it take std::map ? Third party json types? Can I make it work (accept) QString or QVariant/QVarianMap with some extension?
- Dominant language
- C++
- Stars
- 600
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from jinja2cpp/Jinja2Cpp
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in jinja2cpp/Jinja2Cpp
Similar issues
-
`enzymexla.linalg.lu` lowering fails for a tall matrix: the permutation is built with the pivot typeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EnzymeAD/Enzyme-JAX#3286 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/iceberg-cpp#973 ·
Maintainers usually reply within 1 day
-
feature request
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day