Check what is passed to **kwargs in the parsers to avoid silent bugs
Open
Nobody has claimed this yet.
enhancement ✨
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
Typos can lead to parameters being not specified inside parsers and their default value (None) can lead to nasty bugs. I would add checks that the argument passed to kwargs are actually the expected (like customization for spatial-image)
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
Start by locating the parser implementations and the spatial-image customization referenced in the issue. Compare the arguments passed through kwargs with each parser's expected parameters, then verify that unexpected names are reported instead of silently using None; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100