cc @alvarocavalcanti

What is the problem / feature ?

Trying to match the path /v1/accounts/23 against a schema with the following paths throws an error.

paths:
    - "/v1/accounts/{account_id}"
    - "/v1/accounts/{account_id}/subscriptions"

How did it get fixed / implemented ?

Changed the logic around picking from multiple matches to choose the longest api path. This doesn't actually fix #58 but it still improves the situation.

How can someone test / see it ?

Match the path /v1/accounts/23 against a schema with the following paths and see that it matches the /subscriptions one correctly.

paths:
    - "/v1/accounts/{account_id}"
    - "/v1/accounts/{account_id}/subscriptions"

Here is a cute animal picture for your troubles...