Erroneous test result. about path-to-regexp HOT 3 CLOSED

The code on master is passing the test. I have it passing locally too. I’m not sure what you’re referring to when you say the “code on master” has a different result.

from path-to-regexp.

I'm finding it hard to discuss "in reality" here, because in reality these tests pass and /baz does match. Also, you're mentioning two things:

In reality, /baz would not match because options.start defaults to true.

In reality it does match and that's a code functionality of this library, to match this code.

With the code in master, the tokens actually look like the following

Are you saying, that in master, with zero code modifications, the test suite is failing? Can you share something to confirm this?

from path-to-regexp.

Jesus ignore me; I was very tired.

What I thought was happening was parse() returned a different value than what the test file actually registered (for me, both running your code as well as the ported version I was getting the same output, two tokens, one of them with a prefix) but I just realized I hadn't escaped the / in my route. Ignore this.

from path-to-regexp.