Issue 1400 #1729
Merged
Issue 1400 #1729
Conversation
This file contains 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
added 2 commits
June 19, 2023 22:11
… being parsed when csv without headers is loaded
Julias0
commented
Jun 19, 2023
Julias0
commented
Jun 19, 2023
mathiasrw
pushed a commit
that referenced
this pull request
Jun 20, 2023
|
Released as part of v4.1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This contains feature for a new option for csv imports called
raw. Passing that should make sure that the imported values are all strings solving the problem for #1400There is also a bug fix that if CSVs were imported without headers, the numerical values inside the csv would not be parsed into numbers.