Allow changing chars for index 62 and index 63 about lz-string HOT 6 CLOSED

The implementation I suggest for encoding something to URL encode is: LZString.compressToBase64().replace("=","$").replace("/","-") with of course the reverse replace before decoding. With this, you have nothing to URL encode.

I'll push two methods that wrap that. It never hurts. I'll update the documentation once this is in. (And I need to refactor a few things to make the current 'release' version more accessible by removing the version from the file name). I'll do that this weekend.

If you think of better chars than $ and -, I'm all ears.

from lz-string.

I also use $ and - myself as well as replace and reverse replace where needed :)
And like you said, I also think that wrapping it doesn't hurt and will make the code "prettier" 👍

from lz-string.

The version 1.3.5 should do the trick. Let me know.

I'll update the doc soon.

from lz-string.

Doc updated.

from lz-string.

I just looked at your implementation. I was actually hoping for a method which simply lets you set the last 2 chars of _keyStr to whatever you want, which will probably be part of some init step, setting various properties.
btw - since I use compressToUTF16 (I sometimes need to save url safe strings to the localStorage), and not compressToBase64, I can't use the new implementation (compressToEncodedURIComponent uses compressToBase64) and will continue using the replace method myself :/

from lz-string.

I don't understand your issue...

First, yes, I could have done something smarter for compressToEncodedURIComponent instead of basic replaces, but since this method is a preparation for a network operation, I guess wasting a couple of milliseconds here is no big deal and will be insignificant in regard to the network latency. That may not always be the case.

Second, I don't see the point in making the output of compressToUTF16 URL-encoded... Can you elaborate on your needs?

from lz-string.