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
Different from the actual file cursor when processing duplicate headers with header auto #994
Comments
I don't know if it makes sense, but could I fix it with code something like this:
|
Hi @jsakaicribl, What you comment complletly makes sense. Thanks! |
@pokoli Thank you for taking a look the PR and merge. Will this be released with version 5.4.2? When do you think it will be npm package? |
@jsakaicribl Yes, it will be included on the next version, not sure when I will be able to upload it. It depends also if we wait to include more fixes. |
Will 5.4.2 be released soon? |
When processing duplicate headers with header auto, the position of data.meta.cursor will be returned as the position of
cursor
including headers such as _1. But it's different from thecursor
of the actual file. For example, if I execute the test written here below,cursor
will return 21 and an error will occur. However, I think the end of the file is 15, but it seems that thecursor
is returning a cursor at a position that doesn't actually exist.I would appreciate it if you could take a look.
The text was updated successfully, but these errors were encountered: