You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nice work on this small, performant library. Works great!
If you are open to it, I would like to add a PR that adds an additional option for the decode() function where we could set { mode: "all" }. Currently the most extensive option for encoding is with { mode: "extensive" } which makes sense from a semantic perspective that this does not encode every character. Adding "all" would in fact encode every character.
Why?
I was planning to use this to fully url encode email addresses for showing on a web page. This way, mailto: and the email address itself could be fully entity encoded which should prevent all but the most sophisticated email scraper bots.
If this is out of scope for this library, I understand. Feel free to close this as such. Otherwise, let me know and I can open a PR to add this.
The text was updated successfully, but these errors were encountered:
Nice work on this small, performant library. Works great!
If you are open to it, I would like to add a PR that adds an additional option for the
decode()
function where we could set{ mode: "all" }
. Currently the most extensive option for encoding is with{ mode: "extensive" }
which makes sense from a semantic perspective that this does not encode every character. Adding"all"
would in fact encode every character.Why?
I was planning to use this to fully url encode email addresses for showing on a web page. This way,
mailto:
and the email address itself could be fully entity encoded which should prevent all but the most sophisticated email scraper bots.If this is out of scope for this library, I understand. Feel free to close this as such. Otherwise, let me know and I can open a PR to add this.
The text was updated successfully, but these errors were encountered: