You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This doesn't seem very intuitive at first glance. If it's by design, perhaps the docs should be updated.
When an invalid row is encountered, it appears to be removed from the original internal row count before the data-invalid event is emitted. This means each index value really corresponds to the total number of valid rows, not total rows, which presumably the user would need to keep track of while parsing.
This doesn't seem very intuitive at first glance. If it's by design, perhaps the docs should be updated.
When an invalid row is encountered, it appears to be removed from the original internal row count before the
data-invalid
event is emitted. This means eachindex
value really corresponds to the total number of valid rows, not total rows, which presumably the user would need to keep track of while parsing.Thanks for your work on this library.
The text was updated successfully, but these errors were encountered: