Improve error message in case of a misformatted file (#158) #190
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.
add more descriptive error handling regarding poorly formatted files
update version
add dot prefix to json file extentions and ensure list of allowable file types is complete
cleanup error messages and add comments to explain jsonl/json loading logic
cleanup csv/tsv reading allowing use of elif for other file extensions, add comments, and remove unnecessary re-attempt to parse as json
run fillna immediately upon DataFrame creation so that an additional switch is not needed
use only 1 try-except block to catch parsing errors + cleanup error message
separate the json and jsonl cases while still maintaining the same functionality, also include a message to user if jsonl appears to be json or vice versa
fix bug in csv path
use index -1 to get extension from split
black formatting apply
fix black
Co-authored-by: joe-at-openai [email protected]