-
Notifications
You must be signed in to change notification settings - Fork 285
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
"One or more parsing issues" warning but problems() prints nothing #1376
Comments
p.s. I imagine that the complaint that's not getting passed through is something like this: > parse_double(c("", "Manual Posting", "12", "24"))
Warning: 1 parsing failure.
row col expected actual
2 -- a double Manual Posting
[1] NA NA 12 24
attr(,"problems")
# A tibble: 1 x 4
row col expected actual
<int> <int> <chr> <chr>
1 2 NA a double Manual Posting It would be nice to be able to squelch this specifically. |
It looks like you are using Having column specific |
The documentation says that if you don't supply an argument to
Please reopen. |
I cannot reproduce this:
|
Consider the following CSV file. (This is cut down from an actual grade sheet exported from Canvas, with all the real data replaced by fake values, preserving structure.)
The line with "Manual Posting" in the first two assignment columns is junk -- I have no idea what it means or why it's even there -- but naturally enough it makes
read_csv
use character vectors for those columns. That's not what I want so I give a column type spec. No problem there.The bug is that when I give a column type spec, I get a "One or more parsing issues" warning but problems() prints nothing:
The text was updated successfully, but these errors were encountered: