slash at the end of route

[omerts]

Hey,

Currently when there is a slash at the end of a route, the match function returns false. For example:

routeParser('/test').match('/test/') // false

Is this the expected behavior? Shouldn't the above return a truthful value, since the slash at the end doesn't have a real meaning?

[firasdib]

They are technically two different routes, and I believe google would index them as such? I could be wrong though.

[omerts]

@firasdib From what I know, websites will serve the same content if there is or isn't a preceding slash. Just try to add/remove the trailing slash from this issue :).

[firasdib]

@omerts Read this https://webmasters.googleblog.com/2010/04/to-slash-or-not-to-slash.html

[goliatone]

@firasdib while you are technically right it does seem other routers might treat it (wrongly?) as if it was the same route. I guess a note in the documentation would prevent some surprises.

[pietrovismara]

@goliatone Can confirm a note in the documentation would have prevented me some surprises :)