Trailing slash in pathname

[cdoublev]

A route /foo/ is currently matching an url /foo and vice-versa. I suppose that this behavior comes from path-to-regexp and that it will not be changed as FaceySpacey indicated in #63. But:

http://example.com/foo/ (with trailing slash, conventionally a directory)
http://example.com/foo (without trailing slash, conventionally a file)

Google treats each URL above separately (and equally) regardless of whether it’s a file or a directory, or it contains a trailing slash or it doesn’t contain a trailing slash.

https://webmasters.googleblog.com/2010/04/to-slash-or-not-to-slash.html

It obviously has serious SEO implications. Wouldn't be usefull to add something about that in the readme, ie. test /foo === location.pathname || redirect({ type: '/foo/' }), if it would not be handled in RFR?

[cdoublev]

It probably boils down to passing a strict option to pathToAction and use it as the second argument for calling compilePath here.

[ScriptedAlchemy]

Open a PR with your suggestion - if you can Mock up a small unit test for it. Ill also apply the same thing to Rudy