It wouldn't be out of the question to add a decoded version of the path. It'd have to be a new member, though, and perform adequately (maybe a flag to enable it or something.)
But I don't think it's really that pressing of an issue. The question of whether you wish to use decodeURI or unescape is relevant, but I think we can probably just never use unescape. On Thu, Apr 26, 2012 at 07:06, Brandon Benvie <[email protected]> wrote: > It's probably because almost half! of the global objects in JavaScript > (mandated by spec) are functions dedicated to encoding and decoding that > precise type of string, and the node developers didn't want to presuppose > which of those you did or didn't use > > > escape > unescape > encodeURI > decodeURI > encodeURIComponent > decodeURIComponent > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
