Highlights Supported by Deciding Force Parser #163
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.
What
Previously the Deciding Force parser was unable to handle highlights/square brackets. With these additions the parser now removes highlights from the text, records the highlight offsets in the article metadata, and throws errors if improperly formatted highlights or square brackets are found in the text.
How
I iterated through the text file to find "[" and "]" characters, signifying the start and end of a highlight. If a left bracket was found without its corresponding right bracket or vice versa an error is thrown. When a highlight has been closed by a left and right square bracket the highlight is stored and removed from the text. In a final step the highlight text is compared to the article to find its starting index offset. At this stage all the highlight offsets are calculated.
Why
Handle highlights in Deciding Force articles.
Comments