Percent encoding support for URL path

Seems there is no support for percent encoding either unencoded or encoded e.g.

const Path = require('path-parser');
new Path('🦄');

Error: Could not parse path '%F0%9F%A6%84'
    at tokenise (/Users/alextes/code/notepad/js/node_modules/path-parser/dist/cjs/path-parser.js:95:15)
    at new Path (/Users/alextes/code/notepad/js/node_modules/path-parser/dist/cjs/path-parser.js:166:23)

Since percent encoding is allowed in URLs and common in translated routes would you appreciate a PR that supports recognizing % as part of a fragment?

[alextes]

So with https://github.com/router5/router5/issues/63 this got implemented for parameters. This would be about supporting it in the fragment.

Maybe good to share that you call fragment is what the RFC calls path. A little confusing as there’s also URL fragments. From the RFC:

   The following are two example URIs and their component parts:

         foo://example.com:8042/over/there?name=ferret#nose
         \_/   \______________/\_________/ \_________/ \__/
          |           |            |            |        |
       scheme     authority       path        query   fragment
          |   _____________________|__
         / \ /                        \
         urn:example:animal:ferret:nose

I’d suggest updating that to match the RFC which talks about components 😁 .

[troch]

I’m of course happy to put in a PR with that change 😄 .

If you have time, definitely 👍