Different Line endings
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the file-reading and line-splitting logic described in the issue. Verify how CRLF, CR, and LF inputs are handled, including newline characters inside strings; done means supported line endings no longer cause parsing failures.
Written by the indexing model from the issue text.
Description
Right now only Unix line endings are supported. I need to convert all \r\n into \n and then all \r into \n.
Right now it explodes the file on every \n, but if a \n occurs in a string it shouldn’t. Should read the file by line instead maybe.
- Dominant language
- PHP
- Stars
- 1
- Forks
- 0
- 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 Beakerboy/Coveralls-Visualizer
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in Beakerboy/Coveralls-Visualizer
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
grokability/snipe-it#19857 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Authentication / Authorization Feature: Volunteer
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bagisto/bagisto-api#51 ·