-
Notifications
You must be signed in to change notification settings - Fork 1.1k
bugfix/fix ndjson detection #3905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
scanny
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I propose moving this lower down, otherwise LGTM.
Let me know and I can approve it then.
|
Also @rbiseck3 I'd like to see a test for this. Good chance to fill in for the other possible cases, like when it comes with an asserted content-type. |
|
The test suite is well developed, you should be able to do most of it with just adding a case to parameterized tests. |
ced1e8e to
0159ec4
Compare
scanny
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :)
1425726 to
cd1dc47
Compare
a59df4f to
665d3d5
Compare
### Description NDJSON files were being detected as JSON due to having the same mime-type. This adds additional logic to skip mime-type based detection if extension is `.ndjson`
Description
NDJSON files were being detected as JSON due to having the same mime-type. This adds additional logic to skip mime-type based detection if extension is
.ndjson