leanOptions handling potentially brokeen
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 384
- Forks
- 124
- Avg merge
- 22h 28m
- Merged PRs (30d)
- 10
Description
Adding
[leanOptions]
weak.linter.unusedVariables = false
to the lakefile.toml
causes build failures in the literate faces, see commits in an example repo I made:
https://github.com/mo271/WeakLiterate
I have a potential fix prepared, will make a pr shortly.
Contributor guide
No contributing guide indexed for this repository
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 with the [leanOptions] entry in lakefile.toml and reproduce the failure using the linked WeakLiterate example repository and its referenced commits. Compare builds with and without weak.linter.unusedVariables = false; done means the literate faces build successfully with that option enabled.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100