Switch `parsing` for `error`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
Research direction
Start by locating the parsing module and checking where its error types are imported or re-exported. Run the project tests before and after the module rename; the work is done when the error module provides those types and all existing references still build and pass.
Written by the indexing model from the issue text.
Description
parsing just has error types, create error module instead
- Dominant language
- Rust
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from AldaronLau/ranch
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
AldaronLau/ranch#78 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
AldaronLau/ranch#72 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
AldaronLau/ranch#62 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
AldaronLau/ranch#59 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
AldaronLau/ranch#58 ·
All issues in AldaronLau/ranch
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100