RDataException
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No file or test is named. Start by locating reader paths in RData.jl that currently throw error, then determine the intended RData-specific exception scope and available context. Done means the issue's exception type is defined and can carry the current I/O position or top-level element while replacing the relevant generic errors.
Written by the indexing model from the issue text.
Description
It would be nice to throw some RData-specific exception type instead of error, it can also contain some useful information, like current io position or the name of the top-level element being read.
- Dominant language
- Julia
- Stars
- 63
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 JuliaData/RData.jl
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement up for grabs
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in JuliaData/RData.jl
Similar issues
-
documentation priority: high
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TuringLang/Turing.jl#2917 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
30-minutes algorithm any-language codewars dart easy elixir hackerrank hacktoberfest haskell help wanted interview-prep julia leetcode lua open-source r scala students zig
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Huerte/algo-solutions-python#226 ·
Maintainers usually reply within 1 day