[BUG] OpenApi 2 client generator - error parsing when refparameters not separated by slash

Description

In an openAPI 2.0 declaration, if you have two ref parameters not separated by "/" , the client generator send the error :

-attribute paths.'/v1/users/{firstparam}-{secondparam}'. Declared path parameter firstparam}-{secondparam needs to be defined as a path parameter in path or operation level

swagger parser version

2.0.11-OpenAPITools.org-1

OpenAPI declaration file content or url

"paths" : {
    "/v1/users/{firstparam}-{secondparam}" : {
      "get" : {
        "description" : "",
        "operationId" : "xxx",
        "produces" : [ "application/json" ],
        "parameters" : [ {
          "name" : "firstparam",
          "in" : "path",
          "required" : true,
          "type" : "string"
        }, {
          "name" : "secondparam",
          "in" : "path",
          "required" : true,
          "type" : "string"
        } ],

the OpenAPI declaration file has no error in swagger editor

Start by reproducing the failure with the OpenAPI 2.0 paths declaration for /v1/users/{firstparam}-{secondparam} and parser version 2.0.11-OpenAPITools.org-1. Trace the path-parameter parsing and validation that produces the reported error; done means both adjacent path parameters are accepted when they are defined at operation level.