Fix field parse #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For String fields, DBF doesn't always encodes it as UTF-8, normally plain ANSI. So remove 'utf-8' from parameter. For Number fields, parseFloat should be used instead of parseInt.
Contributor
|
It's not always ANSI too, so #7 is more preferrable, though even more brief variant is possible, https://github.com/irandom/node-dbf/commit/66ae4b338070c4615f3faa372d319d1ba4a0d13f. If I manage to add tests and if the author still maintains the package I will request a pull from my fork. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For String fields, DBF doesn't always encodes it as UTF-8, normally plain ANSI. So remove 'utf-8' from parameter.
For Number fields, parseFloat should be used instead of parseInt.