header-includes should be moved outside individual templates
Open
Nobody has claimed this yet.
feature
- Dominant language
- TeX
- Stars
- 1.5k
- Forks
- 517
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
I think it would be reasonable to move this chunk of code outside individual templates:
$for(header-includes)$
$header-includes$
$endfor$
It should be possible to include additional packages for any template. Also, it is easy to miss this, as is the case for arxiv template (which has this chunk missing).
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
Locate the repeated header-includes block in the individual templates and compare it with the arxiv template, where the block is missing. Read how templates are assembled, then verify that additional packages can be included consistently for every template without duplicating the block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100