xmllint opt-out flag
@mwaxmonsky is already working on this.
Since Oct 25, 2024.
- Dominant language
- Python
- Stars
- 25
- Forks
- 67
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Description
As discovered in #601, xmllint is always being checked and run if found. This creates an implicit dependency on xmllint that shouldn't be required for all runs of capgen.
Solution
Add an explicit flag to disable xmllint-ing and associated handling for checking if xmllint is available in the environment if enabled. This way if the flag is not turned on and xmllint is not found in the environment, an error can be generated instead of silently failing and just printing to stdout.
Alternatives (optional)
Discussed an opt-in flag but most uses cases are going to require linting.
Related to (optional)
#601
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.
Assessment
This issue has not been assessed yet.