add handle for index errors during table of contents creation #148
Conversation
This file contains 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
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.
Describe Your Changes
Add exception handling for Index Errors during TOC creation. I elected to skip and warn users about unordered headers because I didn't want to just write a hacky way to try to handle them or throw an error for the sake of workflow.
How Did You Test It
I exported DOC-0013 User Manual in the BodyCheck workspace, as exporting it is how I found this exception. In it, they have an H1 followed by an H3. Figure 1 shows the error I was initially receiving and Figure 2 shows how this addition will log the corresponding warning.
Figure 1
Figure 2