test: Add unit tests for toolbox regex patterns #14
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
SFM changes: * Use `\toc1` instead of `\toc` * Write paragraph marker after chapter markers so Paratext will style Ch1 correctly.
* Also make parens optional in VS_BRIDGE_PATTERN
darcywong00
changed the title
laineyhm
approved these changes
Jan 20, 2023
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.
Resumes work from #13 which I unexpectedly closed when I deleted the base branch.
For investigating issue #11, it will be good to have some unit tests to verify the toolbox.ts regex patterns
To run unit tests
npm run testVS_PATTERN updated to match
\vs 13-14 (b)VS_BRIDGE_PATTERN updated to match 13a-14b
For my testing, I locally set debugFlag to true so I could compare the intermediate .json files just to make sure the regex didn't change existing parsing.