Open eritain opened 5 years ago
Thanks for contributing to this issue. As it has been 2 years since the last activity, we are automatically closing the issue in 30 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please respond before the issue is closed, or post a message on the mailing list. We'll gladly take a look again!
Summary:
CSV ("comma-separated values") can and does represent values that contain commas. It uses ASCII double quotation marks around the value to indicate that the comma is part of the value, not a field separator. For example, a number may be formatted "1,234.56"
Gradebook import ignores the quotation marks, which spreads the value across multiple fields that it's not supposed to be in.
Steps to reproduce:
Expected behavior:
Grades are unchanged.
Actual behavior:
Values exceeding 999 are incorrectly spread across multiple cells. All subsequent values on the same row land in the wrong column.
Additional notes:
Gradebook version history is good, but a rollback function would be better. Much, much better.
There are widely used, tested, freely available libraries that parse CSV correctly.
Fuzz testing would probably have caught this bug.