add feature: include line number in toc parse error message#38
Open
outis wants to merge 3 commits into
Open
Conversation
…e debugged from the command line
…mber can't be converted to an int
Contributor
Author
|
Branch to pull from now includes other fixes (described in commit messages). |
|
Ran into this issue several times today while using the otherwise fantastic pdf.tocgen. Would be great to see this merged into main. |
|
I get a |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, when there's an error parsing a toc entry, it's difficult to find which entry caused the error, as there isn't much context provided in the error message. This commit adds line number information to the error message so users can know which line generated the parse error.