Reader doesn't match path parameter by its description in parameters

[AMalleus]

I have 2 uri described in my openapi spec:

1. /v1/records/{recordId}/
   Where recordId described in parameters as integer

2. /v1/records/export/

I do make a request /v1/records/export/ and my request is matched to /v1/records/{recordId}/. Second uri is just ignored. It seems like it matches first valid path uri described in spec. But this is not right, because next i get a validation error that recordId expected to be integer

So... request /v1/records/export/ must be matched to /v1/records/export/ uri instead of /v1/records/{recordId}/ because first matched uri didn't even pass path parameter validation as it is described

Any solution for this? I don't want to put 2nd uri before 1st and make a dirty hack so it will be working

Maybe this is the issue for openapi-validation-middleware, but path matcher is in this repo