fix : fix broken prefix and suffix diffs generation inside addContext()#4
Conversation
d9948ae to
7751a1c
Compare
Yes, I'm aware - but I believe this should always work as long as the input is valid. I also believe this also applies to your original solution for Fortunately for me, this is good enough for our use-case, as our app is not publicly accessible, and we are in direct contact with all our users - If our user somehow copies a naked surrogate pair (or other invalid text) into our text field, it's not a huge deal in our case. I don't expect this to ever happen, and if it does, then we will deal with it manually, or decide to fix this. |
Moved code here from this pr: #3