How to pass options in Binary for pixelmatch
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7k
- Forks
- 327
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We are using pixelmatch in our Java project and I wanted to understand how should we be passing optional parameters, I do not know if anti aliased pixels are currently ignored by default.
I'm getting issues sometimes in comparison
Expected:
Current:
Diff:
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
No source file or test is named. Start by reviewing pixelmatch's option-passing API and anti-alias handling, then clarify the documented usage and default behavior for Java consumers; done means the optional parameters and anti-alias comparison behavior are unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100