[CI]: Consider More Detailed JinJa2 Template Linting and Checking
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the current CI check that validates generated test files with Black. Read the linked curlylint and Jinjalint rule documentation and compare their coverage with the indentation problem described here. The work is done when the project has agreed detailed Jinja2 checks and those checks are integrated into CI.
Written by the indexing model from the issue text.
Description
After doing numerous JinJa2 template PRs and test file regeneration (and getting caught by a nasty indentation bug), it feels like we could benefit from setting up some linting rules and checks for JinJa2 templates that are a bit more detailed and custom. Right now, we check that the files will produce test files that can be linted by Black, but we don't really do much additional validation.
Marking this as a discussion, since I haven't formed many more thoughts that that around this issue. But I anticipate both more contributors and more changes to templates going forward, so thought I'd make a note here of what I have found so far:
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 1.5k
- PR merge metrics
- No merged PRs in 30d
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.
More from exercism/python
-
Difficulty 1/5 Under an hour Newbie friendliness 1/100
-
x:rep/massive
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100