[0.0.2.10] - 2024-01-17
There was an issue between 2.7 and 2.10, basically I was misunderstanding byteEnd. This has been corrected, byteEnd is now the the last character in the string to be linked from the start of the string. Originally this was just the length of the string replaced, this resulted in odd placements or no placements of the link.
What's Changed:
- Updated the logic to add the startIndex to the endIndex for a proper byteEnd value in the json
Full Changelog: v0.0.2.0...v0.0.2.11