Test/Refactor: split out adobe line splitting logic, added unit tests

[ckhordiasma]

adobe line splitting

in general for text entry, when you have too many words on a single line, the text editor has to decide how and where to break up overflowing words to transition them to the next line. For most words, the editor will just take the last word that doesn't fit and move it over to the next line. However, what should be done in weird cases like hello/world or hello?world ? Should it treat the whole phrase as a single word, or break on the character in between? That is going to depend on the editor, and I found that the browser's text input field and the adobe forms text input fields made different decisions on when to split words to fit into lines better. In order to make sure this is correct, I split out the line break logic into its own function and put in several unit tests against it.

tokenize unit tests

tokenize just takes a bullet and splits it into an array based on whitespace. I wasn't sure if the \s regex character class also handled unicode half-space and other special whitespace characters, so I added unit tests to ensure that it did work.

[justinthelaw]

@ckhordiasma looks like one of your branch's tests failed?

[ckhordiasma]

Ah yeah those were failing from before. We can leave this open until those pass too

[justinthelaw]

Ah yeah those were failing from before. We can leave this open until those pass too

No problem, I don't think it's an issue to merge a branch into a branch of a few tests fail. It's a WIP anyway, and not main branch.