mafintosh / mafintosh/csv-parser
Leading Zero issue for integer
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
* Operating System: Windows 10
* Node Version: 12.18.4
* NPM Version: 6.14.6
* csv-parser Version: Nest Csv Parser : 2.0.4
### Expected Behavior
in csv file the column having values : 50, 60,70,OP, PSE
### Actual Behavior
class Entity { }
delim = ","
after caliing this await this.csvParser.parse(stream, Entity, null, null, { separator: delim });
iam getting values : 050, 060,070,OP, PSE
### How Do We Reproduce?
You can check below file, you will get to know.
[Weehawken_RightAngle_ActiveList.csv](https://github.com/mafintosh/csv-parser/files/7757784/Weehawken_RightAngle_ActiveList.csv)
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 reproducing the issue with the attached Weehawken_RightAngle_ActiveList.csv and the shown csvParser.parse call using csv-parser 2.0.4 on Node 12.18.4. Trace where the values are parsed or transformed and compare the source values with the parsed output. Done means numeric-looking CSV values such as 50, 60, and 70 are not returned with added leading zeros, while OP and PSE remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100